1.4 rc1 bootstrap error

steepee · n00b Joined: 10 Oct 2002 Posts: 3

I have been trying to install 1.4 rc1 on a pentium3 with 128 megs of ram for a few days now and keep getting stuck when I try to do the bootstrap. I get this error everytime...

..-pc-linux-gnu/3.2/../../crtn.o -Wl,-soname -Wl,libgcj.so.3 -o
.libs/libgcj.so.3.0.0
collect2: ld terminated with signal 15 [terminated], core dumped
make[3]: *** [libgcj.la] Error 1
make[3]: Leaving directory
'/var/tmp/portage/gcc-3.2-r1/work/build/i686-pc-linux-gnu/libjava'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory
'/var/tmp/portage/gcc-3.2-r1/work/build/i686-pc-linux-gnu/libjava'
make[1]: *** [all-target-libjava] Error 2
make[1]: Leaving directory '/var/tmp/portage/gcc-3.2-r1/work/build'
make: *** [bootstrap-lean] Error 2

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

(there might be some type-o's in there. I had to enter it all by hand)

I assume it is something to do with java, but i'm not sure.

I've tried it with make.conf set for pentium3 and not set for anything (the default) and get the same results both ways. Although when I recompiled it for the default I didn't reinitilize the partition, so there may have been some residuel files in there continuing to cause the problem, but I to be truthful I have no idea.

Any help would be appriciated.

rac · Posted: Thu Oct 10, 2002 8:06 pm Post subject:

Can you try swapping RAM from another machine?
_________________
For every higher wall, there is a taller ladder

steepee · n00b Joined: 10 Oct 2002 Posts: 3

yeh, I can...just wondering, before I start the whole thing over again, is there a way to start the bootstrap later in the process? It takes a few hours to get to that point in the compile, and if I could continue right before it left off, it might be eaiser to figure things out.

rac · Posted: Thu Oct 10, 2002 8:36 pm Post subject:

You could look into using ccache to start later in the process, but if you're swapping RAM, I think it would be a much more valuable test to do everything exactly the same way. Besides, I don't trust the integrity of the object files that were produced in your previous compilation.
_________________
For every higher wall, there is a taller ladder

steepee · n00b Joined: 10 Oct 2002 Posts: 3

Thanks for the advice. I switched out the ram for a different 128M stick and it compiled without errors. I started it all again from scratch, but this time I didn't change the processor in make.conf. I was being paranoid and didn't want to recompile yet again, so I left it the default. Thanks again for the help