Relocation (Re: Package system)

Sander Vesik sander at haldjas.folklore.ee
Wed Sep 3 11:02:26 PDT 2003


Jeroen Ruigrok/asmodai <asmodai at xxxxxx> wrote:
> -On [20030902 22:52], ibotty (me at xxxxxxxxxx) wrote:
>>this is currently done in the gnustep initializing scripts.
>>they set $LD_LIBRARY_PATH.
> 
> This is such a bad habit, see the following URL for a description which
> I would otherwise have to repeat here:
> 
> http://www.visi.com/~barr/ldpath.html
> 

Sure, consistently using run paths and $ORIGIN (or at least
being able to use ../lib as a runpath) would make the problem
largely go away. Note that it is just plain not possible to
get libtool maintainers to support relative runpaths so you
end up maintaining a patch for ever if you do this. There
are other nice related things one could adopt from Solaris
toolchain and dynlinker.

A hacky bandaid would have something re-write the runpaths 
in executables at package relocation time. Though that is 
nasty, potentially error prone and messes up checksums.

-- 
	Sander

+++ Out of cheese error +++





More information about the Kernel mailing list