got this error while doing an emerge -u world on my 2 day old rc2 install: make[3]: *** [java/awt/AWTEventMulticaster.lo] Error 1 make[3]: *** Waiting for unfinished jobs.... /var/tmp/portage/gcc-3.2.1-r6/work/build/gcc/gcj -B/var/tmp/portage/gcc-3.2.1-r6 /work/build/i686-pc-linux-gnu/libjava/ -B/var/tmp/portage/gcc-3.2.1-r6/work/buil d/gcc/ --encoding=UTF-8 -fclasspath= -fbootclasspath=/var/tmp/portage/gcc-3.2.1- r6/work/build/i686-pc-linux-gnu/libjava -ffloat-store -g -O2 -MD -MT java/awt/Bo rderLayout.lo -MF java/awt/BorderLayout.d -c /var/tmp/portage/gcc-3.2.1-r6/work/ gcc-3.2.1/libjava/java/awt/BorderLayout.java -o java/awt/BorderLayout.o >/dev/nu ll 2>&1 make[3]: Leaving directory `/var/tmp/portage/gcc-3.2.1-r6/work/build/i686-pc-lin ux-gnu/libjava' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/var/tmp/portage/gcc-3.2.1-r6/work/build/i686-pc-lin ux-gnu/libjava' make[1]: *** [all-target-libjava] Error 2 make[1]: Leaving directory `/var/tmp/portage/gcc-3.2.1-r6/work/build' make: *** [bootstrap-lean] Error 2 !!! ERROR: sys-devel/gcc-3.2.1-r6 failed. !!! Function src_compile, Line 284, Exitcode 2 !!! (no error message)
was able to emerge gcc by doing following: USE="-java" emerge gcc
hi. can you provide the full emerge build log: emerge gcc &>gcc-build.log The real error messages occured further up than what is shown in your output.
Looks like a variation on the Line 284 failure I reported in bug 13875.
Created attachment 7290 [details] gcc-build.log.bz2 emerge gcc line 384 build failure example (on Athlon XP from rc2 stage2 with march of athlon-xp and -03)
Oops typo - line 284.
Whit, You error is an IO Error. Thats indicative of a problem at a lowver level than the compiler or the source its compiling. I strongly recommend that you check your filesystems and disks for bad blocks. If you use ext3/2, you'll use something like this: e2fsck -cfv /dev/whatever (make sure your filesystems are unmounted) I had such a problem recently -- it turned out that I have 3 bad blocks!
Matthew, you're right. While mkreiserfs will happily set up one of the partitions, reiserfsck --check immediately bombs complaining "bread: Cannot read a block # 262144". Didn't realize that Reiser was so careless. Have had very good results with it on other systems, but evidently its instructions should caution on the need to check its work immediately.
whit, okay glad we sorted that out. btw, reiserfs is not alone. the same thing happened to me with ext3. i manually do a bad block scan once every few weeks now (paranoid i may be) AlanCB, you need to send more your full build log. I cannot gain any useful information from your snippet as it stands. resolving as NEEDINFO for now. Matt
db fix
