Re: error about build toolchain with crosstool-ng-1.8.0

[loody <miloody at gmail dot com>]

hi all:

2010/9/16 Yann E. MORIN <yann.morin.1998@orange.fr>:
> Arnaud, Loody, All,
>
> On Wednesday 15 September 2010 20:06:39 Arnaud Lacombe wrote:
>> On Wed, Sep 15, 2010 at 2:01 PM, Yann E. MORIN
>> <yann.morin.1998@orange.fr> wrote:
>> > What do you mean by "the new dynamic linker"? Are you referring to gold?
>> > It's not supported.
>> >
>> gold(1) is a linker, not a dynamic linker.
>
> Yeah, I know. :-)
>
>> I think he was speaking
>> about /lib/ld-uClibc.so.0 that the compiler will hardcode in the
>> binary.
>
> That's why I tried to infer a plausible meaning to his/her sentence.
> as it did not make sense to phrase it as the "new dynamic linker".
> There's no such thing as a "new dynamic linker". There's just the
> dynamic linker procided by the C library, which should (and is!) used
> by the toolchain when generating the executables.
>
> Of course, I just realised maybe he/she was trying to run the generated
> binaries on his build machine. That's not gonna work, indeed.
>
> Loody, please clarify what you are trying to do.
first all, I have to apologize my mistake for attaching such big file
over the mailing list, sorry :)
The "new dynamic linker" I mean is is exactly what Arnaud said
"lib/ld-uClibc.so.0".
And I did find it doesn't work when i try to run the generated
binaries on my build machine.
it comes to my mind that I can solve this problem with several ways.
1. chroot -- time-consuming
2. create a link from my /lib/ to sys-root/lib/ld-uClibc.so.0 -- but
it seems I will need to do so for every new toolchain.

So i try to know if there is more convenient way to do so.
appreciate your help,
miloody

--
For unsubscribe information see http://sourceware.org/lists.html#faq