When I try to emerge KDE, I get errors about x11-libs/qt-3.3.3 failed. platform is a IBM X440 Dual Xeon, 4 GB RAM, Serveraid 6m Raidadapter Reproducible: Always Steps to Reproduce: 1.emerge kde 2. 3. Actual Results: it stopped with generators/unix/unixmake2.cpp: In member function `void UnixMakefileGenerator::writeMakeParts(QTextStream&)': generators/unix/unixmake2.cpp:989: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.gentoo.org/> for instructions. The bug is not reproducible, so it is likely a hardware or OS problem. gmake: *** [unixmake2.o] Error 1 qmake failed to build. Aborting. !!! ERROR: x11-libs/qt-3.3.3 failed. !!! Function src_compile, Line 121, Exitcode 2 Expected Results: emerge Creating qmake. Please wait... g++ -c -o project.o -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include/qmake -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_NO_COMPONENT -DQT_NO_STL -DQT_NO_COMPRESS -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/mkspecs/linux-g++ -DHAVE_QCONFIG_CPP project.cpp g++ -c -o property.o -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include/qmake -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_NO_COMPONENT -DQT_NO_STL -DQT_NO_COMPRESS -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/mkspecs/linux-g++ -DHAVE_QCONFIG_CPP property.cpp g++ -c -o main.o -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include/qmake -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_NO_COMPONENT -DQT_NO_STL -DQT_NO_COMPRESS -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/mkspecs/linux-g++ -DHAVE_QCONFIG_CPP main.cpp g++ -c -o makefile.o -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include/qmake -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_NO_COMPONENT -DQT_NO_STL -DQT_NO_COMPRESS -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/mkspecs/linux-g++ -DHAVE_QCONFIG_CPP generators/makefile.cpp g++ -c -o unixmake2.o -I. -Igenerators -Igenerators/unix -Igenerators/win32 -Igenerators/mac -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include/qmake -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/include -DQT_NO_TEXTCODEC -DQT_NO_UNICODETABLES -DQT_NO_COMPONENT -DQT_NO_STL -DQT_NO_COMPRESS -I/var/tmp/portage/qt-3.3.3/work/qt-x11-free-3.3.3/mkspecs/linux-g++ -DHAVE_QCONFIG_CPP generators/unix/unixmake2.cpp generators/unix/unixmake2.cpp: In member function `void UnixMakefileGenerator::writeMakeParts(QTextStream&)': generators/unix/unixmake2.cpp:989: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.gentoo.org/> for instructions. The bug is not reproducible, so it is likely a hardware or OS problem. gmake: *** [unixmake2.o] Error 1 qmake failed to build. Aborting. !!! ERROR: x11-libs/qt-3.3.3 failed. !!! Function src_compile, Line 121, Exitcode 2
Please use New -> Gentoo Linux -> Component: Ebuilds. Infrastructure is not the correct addressee. Did you check for bad ram? Internal compiler errors are in most cases a sign of broken hardware.
Any news on this? Can you also post your "emerge info" output and tru with less aggressive CFLAGS?
As per comment #1, you probably have unstable hardware. If you succeed compiling with less aggressive CFLAGS or something like that, reopen this bug. *** This bug has been marked as a duplicate of 20600 ***