I'm updating qt to 3.3.4-r2 with emerge -uD world It fails: g++ -c -pipe -fno-exceptions -Wall -W -O2 -march=athlon-xp -pipe -D_REENTRANT -fPIC -DQT_SHARED -DQT_TABLET_SUPPORT -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_THREAD_SUPPORT -D_LARGEFILE_SOURCE -D_LARGE_FILES -D_FILE_OFFSET_BITS=64 -DQT_NO_XINERAMA -DQT_DLOPEN_OPENGL -DQT_BUILTIN_GIF_READER=1 -DQT_NO_STYLE_MAC -DQT_NO_STYLE_AQUA -DQT_NO_STYLE_INTERLACE -DQT_NO_STYLE_WINDOWSXP -DQT_NO_STYLE_COMPACT -DQT_NO_STYLE_POCKETPC -I/var/tmp/portage/qt-3.3.4-r2/work/qt-x11-free-3.3.4/mkspecs/linux-g++ -I. -I/usr/include/freetype2 -I3rdparty/opentype -I../include -I/usr/X11R6/include -I.moc/release-shared-mt/ -o .obj/release-shared-mt/qtable.o table/qtable.cpp workspace/qworkspace.cpp: In member function `virtual void QWorkspace::childEvent(QChildEvent*)': workspace/qworkspace.cpp:474: internal compiler error: Aborted 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. make[1]: *** [.obj/release-shared-mt/qworkspace.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make[1]: Leaving directory `/var/tmp/portage/qt-3.3.4-r2/work/qt-x11-free-3.3.4/src' make: *** [sub-src] Error 2 !!! ERROR: x11-libs/qt-3.3.4-r2 failed. !!! Function src_compile, Line 139, Exitcode 2 Reproducible: Always Steps to Reproduce: 1.emerge qt or, for me, emerge -uD world 2. 3. Actual Results: Compiler error - see description. Expected Results: make me a nice qt 3.3.4-r2 Here is my emerge --info: Portage 2.0.51-r15 (default-linux/x86/2004.0, gcc-3.3.5, glibc-2.3.4.20040808-r1, 2.6.9-gentoo-r13 i686) ================================================================= System uname: 2.6.9-gentoo-r13 i686 AMD Athlon(tm) XP 2200+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.2.3-r5,dev-lang/python-2.3.4-r1 [2.3.4 (#1, Feb 8 2005, 09:10:49)] ccache version 2.3 [enabled] dev-lang/python: 2.2.3-r5, 2.3.4-r1 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.8.5-r3, 1.5, 1.6.3, 1.7.9-r1, 1.4_p6, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-O2 -march=athlon-xp -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.1/share/config /usr/kde/3.2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon-xp -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox sfperms" GENTOO_MIRRORS="http://mirror.clarkson.edu/pub/distributions/gentoo/ http://mirror.datapipe.net/gentoo http://open-systems.ufl.edu/mirrors/gentoo http://adelie.polymtl.ca/" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" SYNC="rsync://rsync.namerica.gentoo.org/gentoo-portage" USE="x86 3dnow X alsa apm arts avi berkdb bitmap-fonts bonobo cdr crypt cups curl dvd emboss encode esd f77 fam flac font-server foomaticdb fortran gdbm gif gpm gtk imagemagick imlib ipv6 jack java jpeg kde libg++ libwww mad mikmod mmx motif mozilla mpeg ncurses nptl oggvorbis opengl oss pam pdflib perl png python qt quicktime readline samba sdl slang speex spell ssl svg svga tcltk tcpd tiff truetype truetype-fonts type1-fonts xml xml2 xmms xv zlib video_cards_radeon" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS, PORTDIR_OVERLAY
Your system is either running out of resources during compilation, or you have something hardware going wrong, like bad ram, overheated CPU, etc.
I checked and qt build does bomb out at different places each time. That does point to a hardware issue. The cause of this problem is my new Antec case. It has a funnel to allow cool air (and dust) to move directly to the CPU fan and heatsink. This has been in place since Christmas and it already built up too much dust. In CMOS set up the CPU reported 70 degrees C, so I guess it would be much higher when compiling. A can of air fixed it. Thanks...
