Re: Motivation for -rpath-link

[Daniel Jacobowitz <drow at mvista dot com>]

On Tue, Nov 04, 2003 at 12:08:27PM +0000, Nick Clifton wrote:
> Hi Vladimir,
> 
> > I'm somewhat confused about one sentence in -rpath-link documentaion. It says:
> >
> >    When using ELF or SunOS, one shared library may require another.
> >     [....]
> >     When the linker encounters such a dependency when doing a non-shared, 
> >     non-relocatable link, it will automatically try to locate the required
> >     shared library and include it in the link, if it is not included  
> >     explicitly.
> >
> > Why this behaviour is desired?
> 
> The behaviour is desired because the executable that is being created
> is supposed to be able to run without requiring *any* shared
> libraries.  ie it is completely self-contained.

Hmm, that's not my interpretation of the above.  This happens during
linking of a dynamic executable as well - that's a non-shared,
non-relocatable link, since it produces an ET_EXEC.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer