[uClibc]Confusion about paths
Tobias Anderberg
tobias.anderberg at axis.com
Fri Nov 29 09:58:28 UTC 2002
Markus Pietrek <maillist at fsforth.de> writes:
> Hi
>
> > Pedro Sanchez <psanchez at nortelnetworks.com> writes:
> > > 1. I succesfully generated the cross compiler using the gcc-3.2.1 tool
> > > chain (with some mod's). The tool chain was installed in /opt/uclibc
> > > (TARGET_PATH=/opt/uclibc). This means that if I cross compile my apps,
> > > and get them loaded into my target board, they will look for the
> > > libraries to be living in /opt/uclibc/lib, correct?
> >
> > No. The linker doesn't include absolute path's in the binaries.
>
> What is with the linker options "-rpath" and "-rpath-link" for shared
> libraries? They store additional fixed paths in the binary.
As you say, they stores additional paths to for the runtime linker
to search in. It doesn't store an abosulte path to the _library_,
which the runtime linker is to load.
See ld(1) for more informaion.
--
Tobias Anderberg
Axis Communications AB
More information about the uClibc
mailing list