Emerge + Hardware health: SegFaults, Internal compiler error

[danzvash]

I am trying to update my system (emerge -u world).
For me, this involves building the new KDE (3.0.1).

At first, the emerge segfaulted (signal 11) building kdelibs3.0.1.
I simply tried again, and it worked flawlessly. --------- (!)

Now I am having the same error with kdebase3.0.1 (the next in the queue).

I am getting
- signal 11 [Segmentation fault]
AND
- Internal compiler error

at different points during the build (each time I am simply re-executing "emerge -u world"):

1) First it failed during the build for kcm_css.la.closure.

2) On the next attempt I got:
collect2: ld terminated with signal 11 [Segmentation fault], core dumped
make[3]: *** [kcm_konqhtml.la.closure] Error 1

3) The next time I got:
collect2: ld terminated with signal 11 [Segmentation fault], core dumped
make[4]: *** [kcm_fontinst.la.closure] Error 1

4) This last time I got:
In file included from kcm_crypto_la.all_cpp.cpp:2:
crypto.cpp: In method `void KCryptoConfig::load()':
crypto.cpp:989: Internal compiler error.
crypto.cpp:989: Please submit a full bug report.
crypto.cpp:989: See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
cpp0: output pipe has been closed
make[3]: *** [kcm_crypto_la.all_cpp.lo] Error 1


OK, so my question is:
Does this look like a hardware problem to anybody else?
(i.e. CPU overheating, memory faults)

The fact that the build bombs out at different points each time, and not always with the same fault, does suggest hardware faults - doesn't it?

This is a power system - Athlon XP1800+, 768mb DDR ram, 80gb disk (nowhere near full). I'm not even running X at the moment so I still have 450mb physical RAM untouched.

If you can confirm my suspicions that this is a hardware issue, what are people's suggestions for establishing hardware health? (in terms of soft RAM-testing and CPU temperature issues - anything else)

Any input appreciated.
-Dan

[lx]

Put the covers of your case, it can reduce the temperature. Ofcourse first find out if the temperature is getting to high. Maybe check your memory with memtest86 (see other posts). Somebody also suggested that it might be a problem with certain motherbords and XP chips. Damn hardware problems aren't that common and difficult to detect, powersupply can also be too weak.

How long is your hardware running, in this configuration....you should have problems before if it's overheating / powersupply. Damn,

Hope you will fix it, lX
_________________
"Remember there's a big difference between kneeling down and bending over.", Frank Zappa

[fghellar]

Take a look at this site: http://www.bitwizard.nl/sig11/.
_________________
| www.gentoo.org | www.tldp.org | www.google.com |