On Tue Jun 24, 2008 at 12:25:39 +0200, Stefan Kögel wrote:
Target: i586-suse-linux Configured with: ../configure --enable-threads=posix --prefix=/usr --with-local-prefix=/usr/local --infodir=/usr/share/info --mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib --enable-languages=c,c++,objc,fortran,obj-c++,java --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.1.3 --enable-ssp --disable-libssp --disable-libgcj --with-slibdir=/lib --with-system-zlib --enable-shared --enable-__cxa_atexit --enable-libstdcxx-allocator=new --program-suffix=-4.1 --enable-version-specific-runtime-libs --without-system-libunwind --with-cpu=generic --host=i586-suse-linux Thread model: posix gcc version 4.1.3 20080612 (prerelease) (SUSE Linux)
What I find strange is that the default gcc version is 4.1 and not 4.3 what I would suspect when looking at the package repository of version 11.0. Is gcc-4.1 really ok despite the date seems recent? I would not expect a downgrade when the previous version looks like 4.2.3.
Actually you are right. Suse 11 ships with gcc4.3. I installed gcc4.1 manually. Gcc4.3 generated the same error and I thought I could fix this by using an earlier version of gcc. The building manual states that "version 3.3, 3.4, 4.0, 4.1 or 4.2" of gcc is needed.
4.3 works as well nowadays.
Unfortunately "make oldconfig" in ~/my-l4-build does not fix the problem. Still the same error. Should I consider checking out the module again?
That should not make a difference. Can you go to ~/my-l4-build, do "make V=1 oldconfig" and show the output? Normally, after doing oldconfig, the paths in ~/my-l4-build/Makeconf.bid.local should be updated to the current compiler. Hopefully it can be seen from the output why this might not work.
Adam