William Immendorf wrote: > On Thu, Jul 7, 2011 at 6:29 AM, Frederick Muriithi > <[email protected]> wrote: >> ../../gcc-4.5.2/gcc/c-common.c: In function 'c_common_nodes_and_builtins': >> ../../gcc-4.5.2/gcc/c-common.c:5106: internal compiler error: Segmentation >> fault >> Please submit a full bug report, >> with preprocessed source if appropriate. >> make[2]: *** [c-common.o] Error 1 >> make[1]: *** [all-gcc] Error 2 >> make: *** [all] Error 2 > Ah, so you are getting segfaults (a shorting of "segmentation fault") > There is a big page on them here: > > http://www.bitwizard.nl/sig11/ > > The most common cause of these is because of overclocking the CPU > (increasing the speed of it) and/or bad memory. If you don't know what > overclocking is and/or you don't actually overclock your cpu, then > it's usually a problem with your memory. > > There is a great program that checks for bad memory, called Memtest86+: > > http://www.memtest.org/ > > Download the latest version, burn it, boot into it, and let it run > overnight. If any errors come up, try to remove SIMMs and see if you > can get Memtest to pass, and hopefully get no segfaults when > compiling.
If you are a developer, the most common cause of segfaults is a bug in your code. In this case, I really doubt the segfaults are caused by a gcc programming error. I agree with William that it sounds like a memory problem. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
