On Monday 15 October 2007 09:30:52 am Stuart Howard wrote: > As part of regular updates I have come across an error with gcc, the > system is ~x86. > The error has been occurring for a week or so and my usual wait till > it goes away approach does not seem to be working. Originally the > error was called against a file with reference to fortran so I changed > the use flag to - but no help as the result is as below. > > If someone has a suggestion for a way forward I would appreciate it. > > stu > > > > > > /var/tmp/portage/sys-devel/gcc-4.2.2/work/gcc-4.2.2/gcc/expmed.c: In > function 'expa nd_divmod': > /var/tmp/portage/sys-devel/gcc-4.2.2/work/gcc-4.2.2/gcc/expmed.c:4933: > internal com piler error: in free_list, at lists.c:66 > Please submit a full bug report, > with preprocessed source if appropriate. > See <URL:http://bugs.gentoo.org/> for instructions. > The bug is not reproducible, so it is likely a hardware or OS problem. > make[3]: *** [expmed.o] Error 1 > make[3]: Leaving directory > `/var/tmp/portage/sys-devel/gcc-4.2.2/work/build/gcc' make[2]: *** > [all-stageprofile-gcc] Error 2 > make[2]: Leaving directory > `/var/tmp/portage/sys-devel/gcc-4.2.2/work/build' make[1]: *** > [stageprofile-bubble] Error 2 > make[1]: Leaving directory > `/var/tmp/portage/sys-devel/gcc-4.2.2/work/build' make: *** > [profiledbootstrap] Error 2 > * > * ERROR: sys-devel/gcc-4.2.2 failed. > * Call stack: > * ebuild.sh, line 1695: Called dyn_compile > * ebuild.sh, line 1033: Called qa_call 'src_compile' > * ebuild.sh, line 44: Called src_compile > * ebuild.sh, line 1377: Called toolchain_src_compile > * toolchain.eclass, line 26: Called gcc_src_compile > * toolchain.eclass, line 1546: Called gcc_do_make > * toolchain.eclass, line 1420: Called die > * The specific snippet of code: > * emake \ > * LDFLAGS="${LDFLAGS}" \ > * STAGE1_CFLAGS="${STAGE1_CFLAGS}" \ > * LIBPATH="${LIBPATH}" \ > * BOOT_CFLAGS="${BOOT_CFLAGS}" \ > * ${GCC_MAKE_TARGET} \ > * || die "emake failed with ${GCC_MAKE_TARGET}" > * The die message: > * emake failed with profiledbootstrap > * > * If you need support, post the topmost build error, and the call > stack if relevan t. > * A complete build log is located at > '/var/log/portage/sys-devel:gcc-4.2.2:2007101 5-101943.log'.
Hey Stu, I just upgraded three gentoo boxes using gcc-4.2.2. No issues, aside from a few packages that refuse to compile. What I would recommend is some basic maintenance... Sorry, but is it possible you are seeing heat related issues? Perhaps memory errors? It could be a good time to let memtest exercise your mems... -- From the Desk of: Jerome D. McBride -- [EMAIL PROTECTED] mailing list
