g++ -c -pipe -fno-exceptions -Wall -W -O2 -D_REENTRANT -fPIC -DQT_SHARED -DQT_TABLET_SUPPORT -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_THREAD_SUPPORT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -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 -I/usr/X11R6/include/freetype2 -I../include -I/usr/X11R6/include -I/usr/X11R6/include -I.moc/release-shared-mt/ -I/var/tmp/portage/qt-3.1.0-r1/work/qt-x11-free-3.1.0/mkspecs/linux-g++ -o .obj/release-shared-mt/qiconview.o iconview/qiconview.cpp /var/tmp/portage/qt-3.1.0-r1/work/qt-x11-free-3.1.0/bin/moc workspace/qworkspace.cpp -o .moc/release-shared-mt/qworkspace.moc g++ -c -pipe -fno-exceptions -Wall -W -O2 -D_REENTRANT -fPIC -DQT_SHARED -DQT_TA BLET_SUPPORT -DQT_NO_DEBUG -DQT_THREAD_SUPPORT -DQT_THREAD_SUPPORT -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -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 -I/usr/X11R6/include/freetype2 -I../include -I/usr/X11R6/include -I/usr/X11R6/include -I.moc/release-shared-mt/ -I/var/tmp/portage/qt-3.1.0-r1/work/qt-x11-free-3.1.0/mkspecs/linux-g++ -o .obj/release-shared-mt/qdns.o network/qdns.cpp iconview/qiconview.cpp: In method `void QIconView::slotUpdate()': iconview/qiconview.cpp:3036: Internal compiler error. iconview/qiconview.cpp:3036: Please submit a full bug report. iconview/qiconview.cpp:3036: See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. cpp0: output pipe has been closed make[1]: *** [.obj/release-shared-mt/qiconview.o] Error 1 make[1]: *** Waiting for unfinished jobs.... make[1]: Leaving directory `/var/tmp/portage/qt-3.1.0-r1/work/qt-x11-free-3.1.0/src' make: *** [sub-src] Error 2 !!! ERROR: x11-libs/qt-3.1.0-r1 failed. !!! Function src_compile, Line 82, Exitcode 2 !!! (no error message)
please submit output of 'emerge info' and what gcc-versions your system has/ever had (upgraded from gcc-2.95.3 to gcc-3.2)?
root@minion ian # emerge info Portage 2.0.44 (default-1.0, gcc-2.95.3, glibc-2.2.5-r4,2.2.5-r7) ================================================================= System uname: 2.4.19-gentoo-r10 i686 AMD Athlon(tm) XP 1700+ USE="x86 cups kde libg++ mikmod mmx qtmt xml2 alsa arts berkdb bonobo esd gdbm gif gnome-libs gpm gtk gtkhtml guile imlib java libwww motif mozilla nls oggvorbis opengl pam perl png python qt readline sdl slang ssl svga tcltk tcpd tetex tiff X moznomail xface 3dnow apm avi crypt dvd encode fbcon flash jpeg mpeg ncurses oss pdflib quicktime slp spell tdfx truetype voodoo3 xmms xv" ARCH="x86" COMPILER="" CHOST="i686-pc-linux-gnu" CFLAGS="-march=i686 -O3 -pipe" CXXFLAGS="-march=i686 -O3 -pipe" ACCEPT_KEYWORDS="x86" CONFIG_PROTECT="/etc /var/qmail/control /usr/share/config /usr/kde/2/share/config /usr/kde/3/share/config /usr/share/config:/usr/kde/3/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" MAKEOPTS="-j2" JDK_HOME="" JAVA_HOME="/opt/blackdown-jre-1.3.1" AUTOCLEAN="yes" SYNC="rsync://rsync.gentoo.org/gentoo-portage" GENTOO_MIRRORS="http://www.ibiblio.org/pub/Linux/distributions/gentoo" This particular machine has never had anything other than gcc 2.95. It is a six month old 1.2 system, so I am not sure exactly what version (2.95.3, 2.95.2?) of 2.95 it started with.
Well, an internal compiler error usually has little to do with the code being compiled, unless it's a vey big sourcefile or something that makes the system go out of resources. (Any chance of out-of-memory or out-of-diskpace scenario?) Otherwise it can mean that your hardware is unstable, or that your software is badly setup somehow. Not easy to trace, and not a pleasant prospect in any case :-/ Did you try compiling more than once? Some problems of this class don't always show up, or don't always show up in the same location.
I have 512 MB of ram, and according to df, 14GB of available disk space, so I don't think that this is the reason. I have never had any problems with the hardware and it is not overclocked or anything like that. The motherboard is an MSI which is a relatively decent name, so I doubt that the board is to blame. Plus it has been stable and compiled everything that I have asked it to without complaint for 6 months or so. Also, other packages are compiling without error, including a few after this error, so I would put hardware instability down the scale of probabilities. I did try to build qt 3 times, each time with the exact same error. As for the software being badly set up, that is always a possibility, but what am I likely looking for? Is it the compiler that is likely bad or what? I should point out that this is an upgrade to qt, so I do have a version of qt on my system: * x11-libs/qt Latest version available: 3.1.0-r1 Latest version installed: 3.0.5-r2 Size of downloaded files: 13,062 kB Homepage: http://www.trolltech.com/ Description: QT version 3.1.0 Have there been any significant changes between 3.0.5 and 3.1.0 that could potentially cause this problem? Anything that might place more of an emphasis on a compiler, or other system setup, that 3.0.5 would not have?
Well, what I described above was more of a possible causes list than a full one. Did you try compiling qt more than once to see if this is a 'deterministic' problem? If it fails again, and in the same location, try running make manually in the builddir (with target sub-src). Normally I'd advise trying to compile without optimizations, but with qt that is not easy. So try exporting DEBUG=true to enable a debug build with fewer optimizations, maybe that'll help.
It would seem that the 4th time was the charm. I decided to try to update it again before I tried with the debug option and, for some reason, it worked. So, I guess we can close this bug. Thanks for the help.
Well, this supports my theory of an unstable... something. I wish you luck in tracing it down if it shows up again.
