I'm trying to recompile kdelibs-4.2.3 after upgrading to gcc-4.4.0, also with glibc-2.10.1. I'm not getting very far. So after setting bare minimums in /etc/portage/env/kde-base/kdelibs as so (these are copied from echoes so no quotes display, I tried with and without -fno-strict-aliasing): CFLAGS=-march=opteron-sse3 -pipe -O2 -fno-strict-aliasing CXXFLAGS=-march=opteron-sse3 -pipe -O2 -fno-strict-aliasing LDFLAGS= MAKEOPTS=-j1 I get this: [ 0%] Building CXX object kdecore/CMakeFiles/kdecore.dir/compression/kfilterbase.o In file included from /tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3_build/config.h:186, from /tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3/kdecore/compression/kfilterbase.cpp:20: /tmp/portage/kde-base/kdelibs-4.2.3/work/kdelibs-4.2.3_build/kdecore/kdefakes.h:65: error: new declaration 'char* strcasestr(const char*, const char*)' /usr/include/string.h:367: error: ambiguates old declaration 'const char* strcasestr(const char*, const char*)' make[2]: *** [kdecore/CMakeFiles/kdecore.dir/compression/kfilterbase.o] Error 1 make[1]: *** [kdecore/CMakeFiles/kdecore.dir/all] Error 2 make: *** [all] Error 2 Interestingly enough, during the configure phase, I noticed this: -- Performing Test HAVE_STRCASESTR_PROTO -- Performing Test HAVE_STRCASESTR_PROTO - Failed As I've rebuilt most of my system with gcc-4.4.0 now, I can't properly build kdelibs with gcc-4.3 (after rebuilding cmake so /that/ part works, it fails on a link further into the build), but doing a partial build and comparing that test there, it says Success. That's of course still with glibc-2.10.1, so the test is failing with gcc-4.4, while with gcc-4.3 it succeeds and I get past the part of the compile that's erroring out above. I'll attach my emerge --info, but the above cflags, etc, are what I'm using for this test. (With my normal settings I get further, 12% or so, but of course that's with parallel build, so I'm not sure it's even the same bug. I guess we'll see after this bug's figured out.) I'll also attach the full emerge log. It's obviously not long. Maybe more of the configure output will be helpful.
Created attachment 192203 [details] emerge --info
*** This bug has been marked as a duplicate of bug 270276 ***
Created attachment 192204 [details] emerge log So you know where they came from, note that I added einfos to the /etc/portage/env/* file so I could verify that it was taking the simplified cflags, etc. You'll see them repeat several times in the log, every time portage sources the file, of course.
