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: How the hell is that /ever/ supposed to work?


On 1/26/06, Dave Korn <dave.korn@artimi.com> wrote:
> dk@rainbow /artimi/tools/cygwin/arm-linux/lib> cat libc.so
> /* GNU ld script
>    Use the shared library, but some functions are only in
>    the static library, so try that secondarily.  */
> GROUP ( /usr/local/arm-linux/lib/libc.so.6 /usr/local/arm-linux/lib/libc_nonshared.a )
>
>
>
>   Now I'm really confused.  (I've never looked in a .so file before and so I've only just discovered they can be linker-scripts with
> paths to files in them).  How was this _ever_ supposed to work?  If libc.so is a text file with a hard-coded full path to libc.so.6,
> how could copying libraries into $prefix/$target for a cross build ever work, unless you always used the same $prefix as was used to
> configure the prebuilt-binaries that you've obtained?

When crosstool builds toolchains, it removes the absolute
part of that path using sed.  (Insecure, but what are you gonna do.)

>  And why did it _used_ to work on my old machine?

Maybe you had a symlink there?
- Dan

--
Wine for Windows ISVs: http://kegel.com/wine/isv

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


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