ARM926EJ-S processor, 128MB RAM, running GenLink on Buffalo LinkStation EZ (LS-CL), linux 2.6.22.7, portage 2.1.6.13. emerge sys-devel/gcc begins merging sys-devel/gcc-4.2.4-r1, but xgcc segfaults during the build. this problem does not exist with the sys-devel/gcc-4.2.4 ebuild. workaround: masking sys-devel/gcc-4.2.4-r1 and using gcc-4.2.4 instead. build error: /var/tmp/portage/sys-devel/gcc-4.2.4-r1/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.2.4-r1/work/build/./gcc/ -B/usr/armv5tejl-softfloat-linux-gnueabi/bin/ -B/usr/armv5tejl-softfloat-linux-gnueabi/lib/ -isystem /usr/armv5tejl-softfloat-linux-gnueabi/include -isystem /usr/armv5tejl-softfloat-linux-gnueabi/sys-include -O2 -O2 -pipe -mtune=arm926ej-s -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -I. -I. -I/var/tmp/portage/sys-devel/gcc-4.2.4-r1/work/gcc-4.2.4/gcc -I/var/tmp/portage/sys-devel/gcc-4.2.4-r1/work/gcc-4.2.4/gcc/. -I/var/tmp/portage/sys-devel/gcc-4.2.4-r1/work/gcc-4.2.4/gcc/../include -I/var/tmp/portage/sys-devel/gcc-4.2.4-r1/work/gcc-4.2.4/gcc/../libcpp/include -I/var/tmp/portage/sys-devel/gcc-4.2.4-r1/work/gcc-4.2.4/gcc/../libdecnumber -I../libdecnumber -DSHARED -DL_udivsi3 -xassembler-with-cpp -c /var/tmp/portage/sys-devel/gcc-4.2.4-r1/work/gcc-4.2.4/gcc/config/arm/lib1funcs.asm -o libgcc/./_udivsi3_s.o <built-in>:0: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.gentoo.org/> for instructions. make[4]: *** [libgcc/./_udivsi3_s.o] Error 1 make[4]: *** Waiting for unfinished jobs.... make[5]: Entering directory `/var/tmp/portage/sys-devel/gcc-4.2.4-r1/work/build/gcc' make[5]: `crtend.o' is up to date. make[5]: `crtbeginS.o' is up to date. make[5]: `crtendS.o' is up to date. make[5]: `crtbeginT.o' is up to date. make[5]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.2.4-r1/work/build/gcc' make[4]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.2.4-r1/work/build/gcc' make[3]: *** [stmp-multilib] Error 2 make[3]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.2.4-r1/work/build/gcc' make[2]: *** [all-stage2-gcc] Error 2 make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.2.4-r1/work/build' make[1]: *** [stage2-bubble] Error 2 make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.2.4-r1/work/build' make: *** [bootstrap-lean] Error 2 [31;01m*[0m [31;01m*[0m ERROR: sys-devel/gcc-4.2.4-r1 failed. [31;01m*[0m Call stack: [31;01m*[0m ebuild.sh, line 49: Called src_compile [31;01m*[0m environment, line 4804: Called toolchain_src_compile [31;01m*[0m environment, line 5329: Called gcc_src_compile [31;01m*[0m environment, line 3058: Called gcc_do_make [31;01m*[0m environment, line 2848: Called die [31;01m*[0m The specific snippet of code: [31;01m*[0m emake LDFLAGS="${LDFLAGS}" STAGE1_CFLAGS="${STAGE1_CFLAGS}" LIBPATH="${LIBPATH}" BOOT_CFLAGS="${BOOT_CFLAGS}" ${GCC_MAKE_TARGET} || die "emake failed with ${GCC_MAKE_TARGET}"; [31;01m*[0m The die message: [31;01m*[0m emake failed with bootstrap-lean [31;01m*[0m [31;01m*[0m If you need support, post the topmost build error, and the call stack if relevant. [31;01m*[0m A complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.2.4-r1/temp/build.log'. [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/sys-devel/gcc-4.2.4-r1/temp/environment'. [31;01m*[0m
Try with the latest stable version of gcc.
