booted and installed stage1 from cd, and building of raidtools fails during 'emerge system' the message is: gcc -o mkpw mkpw.o parser.o raidlib.o version.o raid_io.o popt.o parser.o: file no trecognized: File truncated collect2: ld returned 1 exit status make: *** [mkpw] Error 1 make: *** Waiting for unfinished jobs.... !!! ERROR: The ebuild did not complete successfully. !!! Function src_compile, Line 4, Exitcode 2 !!! (no error message) -------- i checked /var/tmp/portage/raidtools-0.90-r2/work/raidtools-0.90, and the parser.o there is not empty (5136 bytes) that bothers me, is that I can build the parser.o manually and it works! even if I enable all flags that the ebuild does: gcc -mcpu=i686 -O3 -pipe -Wall -DMD_VERSION=\""raidtools-0.90"\" -c -o parser.o parser.c In other words, it ain't the -mcpu=i686 -O3 flags that kill it! The system is a AMD Duron 800Mhz w/192Mb ram
i can't seem to reproduce this.. what version of portage were you using at the time?
I'm not sure which version of portage I was using, but I installed with this iso: http://www.ibiblio.org/pub/Linux/distributions/gentoo/releases/build/1.2/gentoo-ix86-1.2.iso And this happened the day the bug was reported; that's as specific as I can be! On a sidenote, after emerge system (which game me this error) and a emerge rsync; emerge --update world, raidtools seems to build fine as it should! :o
yeah... i think the problem was the portage version used. with a 1.2 bootstap you need to update portage first (or else other things break too).
please reopen it, i've the same problem portagetree 28.9.2002 1.2 iso version gcc -march=i686 -O3 got the same error message
don't know why, but the 2nd try: emerge system works now
the same happens to me: I installed 5 gentoo 1.2 systems during the last 2 months and all stopped during "emerge system" on raidtools 0.90. Restarting emerge system again after it stopped the first time will work. I do not hink it is a CFLAGS related issue since the 5 machines were all of different types (P4, Duron, k6, P3, Celeron). Please also note that the last one was built three days ago (16/1/2003). Anyone have any idea about this? Does this happen also with 1.4rc2 ? Bye, Alessandro
I have nothing to go on unless you can send me a full build log.
db fix
