I'm installing Gentoo on an old IBM-thinkpad (without a CD-ROM). While doing an 'emerge system' I get segmentation fault when compiling gcc-3.2.3-r3, see then output below: ------------- stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/ -c -DIN_GCC -march=pentium2 -pipe -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -DHAVE_CONFIG_H -I. -Icp -I/var/tmp/portage/gcc-3.2.3-r3/work/gcc-3.2.3/gcc -I/var/tmp/portage/gcc-3.2.3-r3/work/gcc-3.2.3/gcc/cp -I/var/tmp/portage/gcc-3.2.3-r3/work/gcc-3.2.3/gcc/config -I/var/tmp/portage/gcc-3.2.3-r3/work/gcc-3.2.3/gcc/../include \ /var/tmp/portage/gcc-3.2.3-r3/work/gcc-3.2.3/gcc/cp/parse.c -o cp/parse.o stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/ -c -DIN_GCC -march=pentium2 -pipe -O2 -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -DHAVE_CONFIG_H -I. -Icp -I/var/tmp/portage/gcc-3.2.3-r3/work/gcc-3.2.3/gcc -I/var/tmp/portage/gcc-3.2.3-r3/work/gcc-3.2.3/gcc/cp -I/var/tmp/portage/gcc-3.2.3-r3/work/gcc-3.2.3/gcc/config -I/var/tmp/portage/gcc-3.2.3-r3/work/gcc-3.2.3/gcc/../include /var/tmp/portage/gcc-3.2.3-r3/work/gcc-3.2.3/gcc/cp/ptree.c -o cp/ptree.o /var/tmp/portage/gcc-3.2.3-r3/work/gcc-3.2.3/gcc/cp/ptree.c:-8: internal error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.gentoo.org/> for instructions. make[2]: *** [cp/ptree.o] Error 1 make[2]: Leaving directory `/var/tmp/portage/gcc-3.2.3-r3/work/build/gcc' make[1]: *** [stage2_build] Error 2 make[1]: Leaving directory `/var/tmp/portage/gcc-3.2.3-r3/work/build/gcc' make: *** [bootstrap-lean] Error 2 !!! ERROR: sys-devel/gcc-3.2.3-r3 failed. !!! Function src_compile, Line 411, Exitcode 2 !!! (no error message) ------------- Reproducible: Always Steps to Reproduce: 1. Get an old IBM-Thinkpad (laptop) without a CD-ROM. 2. Use slackware floppies to setup linux and networking. 3. Setup partitions and do chroot accordingly. 4. Unpack stage-2 tar-ball. 5. emerge sync 6. emerge system 7. ...study crash output...
Come to think of that it may be lack of memory that causes the seg.fault. I'll try with a less aggressive flag (e.g -O).
Yes, that was the problem, i.e memory exhaustion.