I'm unable to emerge gcc:
17012 all allocated states, 101385 all allocated arcs
20258 all allocated alternative states
4765 all transition comb vector els, 13107 all trans table els
4765 all state alts comb vector els, 13107 all state alts table els
13107 all min delay table els
0 locked states num
transformation: 0.016001, building DFA: 7.968497
DFA minimization: 0.468029, making insn equivalence: 0.000000
all automaton generation: 8.536533, output: 0.144009
/bin/sh /var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/move-if-change
tmp-attrtab.c insn-attrtab.c
echo timestamp > s-attrtab
stage1/xgcc -Bstage1/ -B/usr/i686-pc-linux-gnu/bin/ -O2
-march=pentium4 -pipe -fprofile-generate -DIN_GCC -W -Wall -Wwrite-strings
-Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long
-Wold-style-definition -DHAVE_CONFIG_H -I. -I.
-I/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc
-I/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/.
-I/var/tmp/portage/gcc-3.4.4-r1/work/gcc-3.4.4/gcc/../include -c
insn-attrtab.c \
-o insn-attrtab.o
cc1: out of memory allocating 8579592 bytes after a total of 7716864
bytes
make[2]: *** [insn-attrtab.o] Error 1
make[2]: Leaving directory
`/var/tmp/portage/gcc-3.4.4-r1/work/build/gcc'
make[1]: *** [stageprofile_build] Error 2
make[1]: Leaving directory
`/var/tmp/portage/gcc-3.4.4-r1/work/build/gcc'
make: *** [profiledbootstrap] Error 2
!!! ERROR: sys-devel/gcc-3.4.4-r1 failed.
!!! Function gcc_do_make, Line 1339, Exitcode 2
!!! emake failed with profiledbootstrap
!!! If you need support, post the topmost build error, NOT this status
message.
The problem appeared when emerging -DNu world. It failed with kpdf. Then
I tried to emerge binutils glibc gcc and it failed at gcc.
Assuming a hardware problem, I tried a script I read about on a recent
thread:
http://people.redhat.com/dledford/memtest.html
The script executed without a whisper.
The box has 1GB RAM, P4 3GHz, no overclocking. The system is up to date.
revdep-rebuild seems happy, except for wanting to re-emerge
openoffice-bin, always.
What else can I do? Is there some other test for hw failure? I can't try
memtest now (I'm away from the box) but it didn't report errors last time
I checked, not too long ago.
--
Jorge Almeida
--
gentoo-user@gentoo.org mailing list
