[uClibc]Problem compiling libstcd++

[Andrew Derrick Balsa]

Hi Henri,

Just checking, what are your target and host?

1) How did you specify target and host when trying to build the toolchain?

2) where did you unpack the tarballs?

3) Did you add the path to the newly created compiler to the PATH?

4) What steps did you follow?

5) did you try erasing the whole thing and re-unpacking your binutils, gcc, 
glibc tarballs? 

From your error message below it seems you specified i386 as the target for 
you gcc cross-compiler. Is that really what you wanted?

G´luck,

Andrew

On Tuesday 06 May 2003 03:04, Henri van Riel wrote:
> Hello Andrew,
>
> Sunday, May 4, 2003, 7:00:22 PM, you wrote:
>
> ADB> Hi Henri,
>
> ADB> Since Erik may not be immediately available, here is a tip:
>
> ADB> On Sunday 04 May 2003 19:19, Henri van Riel wrote:
> ADB> ...
>
> >> /usr/src/toolchain/gcc-3.2/toolchain/bin/i386-uclibc-ranlib libiberty.a
> >> make[2]: /usr/src/toolchain/gcc-3.2/toolchain/bin/i386-uclibc-ranlib:
> >> Command not found make[2]: *** [libiberty.a] Error 127
>
> ADB> That´s typically a PATH problem. Try:
> ADB> export PATH=$PATH:/wherever_you_put_whatever_is_missing
>
> ADB> It takes a little bit of trial-and-error.
>
> Hmmm... I don't know. It seems the first part of the path
> (/usr/src/toolchain/gcc-3.2/toolchain) is derived from the current
> directory. The rest of the path (/bin/) is added during build.
>
> I don't think that changing the path or adding anything to it will
> solve this because the path to i386-uclibc-ranlib is a full path (not
> relative).
>
> Thanks for the idea anyway.
>
> It's strange though that 'everybody' seems to be able to build the
> toolchain without much problems.
>
> I'm running RedHat 7.3 by the way (straight out of the box) and
> gcc-3.2. I did compile the uClibc wrappers without a problem and
> several libraries and programs. It's just this toolchain...

-- 
André Derrick Balsa (Andrew)
andrebalsa at mailingaddress.org