basedir-spec issue

[Laszlo Peter]

We're going way off topic here, but
export LDFLAGS="--rpath=$libdir" (or '${ORIGIN}/../lib')
before you build has [almost] the same effect as setting
LD_LIBRARY_PATH to $libdir every time you run the build.
Except that the latter also affects every other binary
and may cause nasty conflicts, even security issues if
done incorrectly.

Laca

On Tue, 2004-05-11 at 11:18, Rodney Dawes wrote:
> Somehow I think manually editing the compile command line counts as
> "fiddling". :)
> 
> -- dobey
> 
> On Hën , 2004-05-10 at 23:30 +0100, Mike Hearn wrote:
> > On Mon, 10 May 2004 09:11:49 -0400, Rodney Dawes wrote:
> > > The rpath stuff only gets set
> > > properly if the .la files are available for libtool to use, which aren't
> > > needed on linux. Distributions like Red Hat, have started to get rid of
> > > them completely.
> > 
> > If you assume an FHS layout then you can do this:
> > 
> > --rpath='${ORIGIN}/../lib' 
> > 
> > which will cause a program /opt/bin/foo to look in /opt/lib for its
> > libraries.
> > 
> > This is a little known trick. It is however entirely standard (it's a part
> > of the ELF spec). Maybe this is what you are looking for?
> > 
> > apbuild sets this automatically on the grounds that it's nearly always the
> > right thing to do.
> > 
> > thanks -mike
> 
> 
> ______________________________________________________________________
> _______________________________________________
> xdg mailing list
> xdg at freedesktop.org
> http://freedesktop.org/mailman/listinfo/xdg
  FIXIT at THESOURCE