emerge kde-base/kdepim has this problem a short way into compilation: [snip] i686-pc-linux-gnu-gcc -I../include -I./../include -mcpu=i686 -march=i686 -O3 -pipe -Wall -c inetserial.c -fPIC -DPIC -o inetserial.o i686-pc-linux-gnu-gcc: Internal compiler error: program cc1 got fatal signal 11 make: *** [install-datebook.o] Error 1 make: *** Waiting for unfinished jobs.... mv -f inetserial.o .libs/inetserial.lo i686-pc-linux-gnu-gcc -I../include -I./../include -mcpu=i686 -march=i686 -O3 -pipe -Wall -c inetserial.c -o inetserial.o >/dev/null 2>&1 mv -f .libs/inetserial.lo inetserial.lo /bin/sh ../libtool --mode=compile i686-pc-linux-gnu-gcc -I../include -I./../include -mcpu=i686 -march=i686 -O3 -pipe -Wall -c slp.c rm -f .libs/slp.lo i686-pc-linux-gnu-gcc -I../include -I./../include -mcpu=i686 -march=i686 -O3 -pipe -Wall -c slp.c -fPIC -DPIC -o slp.o i686-pc-linux-gnu-gcc: Internal compiler error: program cc1 got fatal signal 11 make[1]: *** [slp.lo] Error 1 make[1]: Leaving directory `/var/tmp/portage/pilot-link-0.9.6-r3/work/pilot-link-0.9.6/libsock' make: *** [libsock/libpisock.la] Error 2 cd ./libsock ; make libpisock.la make[1]: Entering directory `/var/tmp/portage/pilot-link-0.9.6-r3/work/pilot-link-0.9.6/libsock' /bin/sh ../libtool --mode=compile i686-pc-linux-gnu-gcc -I../include -I./../include -mcpu=i686 -march=i686 -O3 -pipe -Wall -c slp.c rm -f .libs/slp.lo i686-pc-linux-gnu-gcc -I../include -I./../include -mcpu=i686 -march=i686 -O3 -pipe -Wall -c slp.c -fPIC -DPIC -o slp.o i686-pc-linux-gnu-gcc: Internal compiler error: program cc1 got fatal signal 11 make[1]: *** [slp.lo] Error 1 make[1]: Leaving directory `/var/tmp/portage/pilot-link-0.9.6-r3/work/pilot-link-0.9.6/libsock' make: *** [libsock/libpisock.la] Error 2 !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 29, Exitcode 2 !!! (no error message) !!! emerge aborting on /usr/portage/dev-libs/pilot-link/pilot-link-0.9.6-r3.ebuild .
1. As you can see at the end of your post, the error is while compiling dev-util/pilot-link, which is a dependency of kdepim but is not itself related to kde. 2. Your compiler recieving a signal 11 isn't, or shouldn't be, related to th compilation itself. It looks like some internal compiler error - I remeber someone complaining on irc #gentoo about his compiler recieving signal 11, and it turned out to be flaky ram. Not a cheery thought. So, maybe you should try rebooting and compiling again. If the same problem comes up at exactly the same location, my analysis may be incorrect, but I'm pretty sure. So please try that.
Tim Haughton just wrote me saying he solved his problem. so I'm closing it. The details of his report follow.---I'm pretty convinced that the problem is not flaky RAM, as I've done thorough tests with a couple of good memory checkers. But I actually resolved the problem about 15 minutes ago.
Tim Haughton just wrote me saying he solved his problem. so I'm closing it. The details of his report follow.---I'm pretty convinced that the problem is not flaky RAM, as I've done thorough tests with a couple of good memory checkers. But I actually resolved the problem about 15 minutes ago. I should have really realised this before sending the bug report, but my memory is like a sieve. - This might be a handy thing to note for you folks on the support side:I have an ASUS A7M266 motherboard, with an Athlon 1.13 gig.I first came across this problem when I gave XP a try on this machine. On 2 different CDs, the installation would always go wrong while copying the files across to the HDD. It would say the file didn't copy properly, and the disk maybe corrupt.I found an obscure reference to this problem on the web site where I got the mobo from. It said that in order to install XP, I had to declock the front side bus from 266 to 200, which has the knock on effect of declocking my processor down to 850MHz. Once it was installed, I could crank it back up again. Sure enough, it worked.It took me a few late nights, cups of coffee, and failed installs of Gentoo to remember this problem. So I did the same thing, declocked the processor and fsb, and sure enough, it installed first time. When the installation was complete, I cranked it back up to full steam and everything was fine.Shortly after I made the bug report, I tried the same thing. Sure enough, no problems.There seems to be an issue with gcc and this mobo. I'm not sure what it is, I'm not even sure where to start looking for an answer. But at least you might be able to recant this solution to fellow sufferers.
