> -----Message d'origine-----
> De: Ulrich Drepper [SMTP:[EMAIL PROTECTED]
> Date: jeudi 28 janvier 1999 00:54
> À: Jules Bean
> Cc: Alexandre Oliva; Debian Developers; [EMAIL PROTECTED]
> Objet: Re: -rpath with libtool and Debian Linux
>
> Jules Bean <[EMAIL PROTECTED]> writes:
>
> > rpath is broken. You said as much yourself. rpath is broken
> because it
> > *overrides* all other sorts of library searching.
>
> I think people here do not know about $ORIGIN. This allows to define
> relative rpaths. E.g., a package with a program foo and a library
> libbar.so where foo is installed in $PATH/bin and libbar.so is defined
> in $PATH/lib should use
>
> -rpath \$ORIGIN/../lib
>
> The $ORIGIN is defined relative to the location of the object
> containing the reference.
>
> This is available in Solaris 7 (maybe 2.6?) and Linux w/ glibc 2.1.
>
This is the perfect way of doing if the same package install a common
shared library and a set of programs using it; then relative paths are
OK. By this does not solve the problem of finding independently
installed libraries or system ones... There -rpath will force to use the
absolute path of these libraries on the development system and if
installed as a binary package, these may be in slightly differing places
(I'm sure there is system libs that are in /usr/lib in some Linux
distribs but in /lib or /usr/local/lib in others...)
AFAIK this is the subject of this whole thread about -rpath: how could
we create binary distributions that WORK... (other than statically
linking all executables of course...)
Regards,
Bernard
------------------------------------------------------------------------
------
Bernard Dautrevaux
Microprocess Ingéniérie
97 bis, rue de Colombes
92400 COURBEVOIE
FRANCE
Tel: +33 (0) 1 47 68 80 80
Fax: +33 (0) 1 47 88 97 85
e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED]
------------------------------------------------------------------------
------
