bootstrap install barfed at making cstringi.o What next?

[thomson]

Hi,

doing a 'do everything' install on an Toshiba 730XCDT laptop (150Mhz PMMX, with a 6 Gig HD, 80M RAM. Slow? you bet.....)

When I start the portage/bootstrap.sh, it goes fine for 9-10 hours, and then barfs with the following:


------------------------------------------------

make [3]: Leaving directory `/home/tmp/portage/gcc-2.95.3-r7/work/gcc-2.95.3/i586-pc-linux-gnu/libio'
test x"yes" !=xyes || \
/home/tmp/portage/gcc-2.95.3-r7/work/gcc-2.95.3/gcc/xgcc -B/home/tmp/portage/gcc-2.95.3-r7/work/gcc-2.95.3/gcc/ -B/usr/i586-pc-linux-gnu/bin/ -c -march=i586 -pipe -fvtable-thunks -D_GNU_SOURCE -fno-implicit-templates -i. -I./stl -I../libio -I./../libio -nostdinc++ -D_IO_MTSAFE_IO -fpic cstringi.cc -o pic/cstringi.o
Assembler messages:
FATAL: can't create pic/cstringi.o: No such file or directory
cstringi.cc:7 output pipe has been closed
make[2]: *** [cstringi.o] Error 1
make[2]: *** Waiting for unfinished jobs....
touch stamp-picdir
make[2]: *** Waiting for unfinished jobs....
make[2]: Leaving directory `/home/tmp/portage/gcc-2.95.3-r7/work/gcc-2.95.3/i596-pc-linux-gnu/libstdc++'
make[1]: *** [all-target-libstdc++] Error 2
make[1]: Leaving directory `/home/tmp/portage/gcc-2.95.3-r7/work/gcc-2.95.3'
make: *** [bootstrap-lean] Error 2

!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line 33, Exitcode 2
!!! (no error message)

(none) portage #


------------------------------------------------

# find /home/tmp/portage -iname pic

/home/tmp/portage/gcc-2.95.3-r7/work/gcc-2.95.3/libiberty/pic
/home/tmp/portage/gcc-2.95.3-r7/work/gcc-2.95.3/i586-pc-linux-gnu/libio/stdio/pic
/home/tmp/portage/gcc-2.95.3-r7/work/gcc-2.95.3/i586-pc-linux-gnu/libiberty/pic
/home/tmp/portage/gcc-2.95.3-r7/work/gcc-2.95.3/i586-pc-linux-gnu/libstdc++/pic

-----------------------------------------------

This has happened twice now, so it's repeatable.

I'm kinda new to this. What do I do next?

Assuming that this is easily fixable, do I have to start the whole scripts/bootstrap.sh process all over again? or is there a good way to restart it where it barfed?

thx!

[rac]

What does "df" say about how much free disk space you have on your various partitions? How did you partition your drive? And, last of all, (don't shoot the messenger) while there are some ways to figure out where you are and manually complete the bootstrap process, it's definitely not something you want to be doing on a first install, especially if you are having problems compiling gcc, which it looks like you are.
_________________
For every higher wall, there is a taller ladder

[thomson]

not sure the previous posted...grrr....


within chroot:

(none) / # df -h

df: cannot read table of mounted filesystems: No such file or directory.

in non-chroot shell:

# df -h

Filesystem Size Used Available Use% Mounted on
rootfs 20.1M 18.1M 2.1M 90% /
/dev/root 20.1M 18.1M 2.1M 90% /
/dev/hda5 1.5G 262.3M 1.3G 17% /g
/dev/hda1 379.6M 8.0M 351.9M 2% /g/boot
/dev/hda8 1.1G 144.0k 1.1G 0% /g/home
/dev/hda7 2.7G 96.4M 2.6G 4% /g/home
/dev/cdroms/cdrom0 135.5M 135.5M 0 100% /mnt/cdrom


also, I have set

export PORTAGE_TMPDIR="/home/tmp"

partition table is

/dev/hda1 /boot ext3
/dev/hda5 / xfs
/dev/hda6 swap
/dev/hda8 /usr/src xfs
/dev/hda7 /home xfs

It's ok about the start all over again.

thx

[rac]

This is a bit of a long shot, and I apologize profusely in advance if I cause you to waste more time. I have bootstrapped Gentoo on a P133 before, and I know how frustrating it is for people to cavalierly say "oh just rebootstrap".

That being said, I fed your error message into google, and came up with the following message: http://gcc.gnu.org/ml/gcc-bugs/1999-11/msg00444.html.

It's almost three years old, but it looks strikingly similar to your situation. So, armed with "nano -w", can you edit the gcc ebuild, which is located in /usr/portage/sys-devel/gcc/gcc-2.95.3-r7.ebuild, after the "emerge sync" step and before you run bootstrap.sh? Change every occurrence (I count 2) of "emake" to "make". Then try running bootstrap.sh again. I really hope it works.

P.S. As I was previewing this, I think I saw you get frustrated and double-post. If that's so, I'll delete one of them for you.
_________________
For every higher wall, there is a taller ladder

[thomson]

ok, I'll give it a try, and let you know tomorrow night, or maybe wednesday <g>.

Thanks for deleting the first.

g'nite

[thomson]

Well, I started over (I did not repartition, tho I did reformat), made the changes you suggested (emake to make, 2 occurances), and am going on 21.5 hours now after starting bootstrap.sh.

FWIW the lines coming across the screen are now like:

/stage2/xgcc -Bstage2/ -B/usr/i586-pc-linux-gnu/bin/ -c -DIN_GCC -O2 -march=i586 -pipe -W -Wall -I. -I.. -I. -I./.. -I./../config -I./../../inclue ste.c

and similar, one about every 15s or so.

Hope this is a good sign?

The only thing I can think of that I did different other than changing the emakes to makes is that there's only one console open this go round.

[thomson]

correction...

the lines going across the screen are like

stage2/xgcc -Bstage2/ <etc> no forward slash at the front of the line.

[rac]

gcc gets compiled twice during bootstrap.sh, so I don't know which one this is, but if it's still going longer than you've gone before, then it sounds like good news to me. If the stage 2 compiler is the active one, you are over 2/3 of the way through this gcc compilation.
_________________
For every higher wall, there is a taller ladder

[thomson]

Maybe if I stay here and glare at it it'll go faster?

I'm afraid to leave and do something else because then it'll barf.

Superstitous? me? nah.

[thomson]

ok. 22 h 15 min, get a root prompt and no error messages on screen. Ergo, I believe a successful conclusion to stage 2....

Should this be put into bugzilla as a bug?

Should I make a tar??

What's the tar switches to create (and extract) a full archive with all the permissions and owners and groups and dates and all that preserved?

tar cvpf <to create> ?

tar xvpf <to extract> ?

thx!

[rac]