Re: Bill's script and glibc-2.2.2. Updated patch.

[Dan Kegel <dkegel at ixiacom dot com>]

Dan Kegel wrote:
> Getting there!  Now I'm running into the problem Bill
> described in http://sources.redhat.com/ml/crossgcc/2001-11/msg00180.html,
> which turns out to be a problem configuring libiberty in libstdc++;
> build-gcc/$TARGET/libiberty/config.log shows that
> gcc couldn't open crt1.o.  Well, guess that's a problem for another day.
> My current script attached.

OK, configuring gcc to just build a c compiler lets the build finish,
but the c compiler it produces can't compile c programs (and this
is the cause of the c++ compiler build failure):

$ p/bin/powerpc-linux-gcc hello.c
/home3/dank/bg/p/powerpc-linux/bin/ld: cannot open crt1.o: No such file or directory
collect2: ld returned 1 exit status

$ find p -name crt1.o
p/powerpc-linux/usr/lib/crt1.o

$ p/bin/powerpc-linux-gcc -print-search-dirs | grep libraries | tr : '\012'
/home3/dank/bg/p/lib/gcc-lib/powerpc-linux/2.95.3/
/usr/lib/gcc/powerpc-linux/2.95.3/
/home3/dank/bg/p/powerpc-linux/lib/powerpc-linux/2.95.3/
/home3/dank/bg/p/powerpc-linux/lib/

So the glibc build put it in $prefix/$target/usr/lib, but the compiler's only looking in $prefix/$target/lib.

So the failure is that, when I set --prefix=/usr in the glibc configure
as required, I failed to also adjust the prefix for gcc.
And maybe for binutils.  This is looking a bit messy...


------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com