This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: Linker question


Thanks Dimitry,

I presume that since I'm building on an i686 for an i386 that potentially I
could link to the host libraries and not notice it before get some strange
behavior on the target? 

If I'm right in my previous statement, could you then suggest a simple test
that I can do to verify that I'm linking with the correct libraries? 

You advise is much appreciated

Best regards,
Thomas

-----Original Message-----
From: Dimitry Andric [mailto:dimitry@andric.com] 
Sent: Tuesday, January 23, 2007 11:03 AM
To: Thomas Olsen
Cc: crossgcc@sources.redhat.com
Subject: Re: Linker question

Thomas Olsen wrote:
> I have built a toolchain using the crosstool-0.43 on an i686 host for an
> i386 target.
...
> and afterwards doing a i386-pc-linux-gnu-readelf it reports:
>             Requesting program interpreter: 
>             /lib/ld-linux.so.2
> 
> I would have expected to see something like in
> /opt/crosstool/gcc-3.4.3-glibc-2.3.4/
> gcc-3.4.3-glibc-2.3.4/lib/ld-linux.so.2

On your *target*, the dynamic linker would most probably be in /lib, not
in /opt/crosstool or wherever, so this is perfectly normal.

Try to think of it as a "virtual root", or something like that. :)


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]