> From: mark benedetto king [mailto:mbk@lowlatency.com]
> Sent: Friday, September 12, 2003 7:34 PM
> On Sat, Sep 13, 2003 at 01:29:25AM +1000, Anthony Baxter wrote:
> >
> > >>> "Sander Striker" wrote
> > > LDFLAGS=-R/opt/local/BerkeleyDB4/lib; export LDFLAGS
> > > ./configure ...
> > >
> > > That's usually how it's done. I would like to add the -R flags,
> > > but I'm not sure if that is going to fly with everyone.
> >
> > I can't see why not - if you specify that the berkeley libs are in
> > a particular directory, surely the whole build process should "make
> > this work"...
> >
>
> There is a camp that believes that /etc/ld.so.conf is the place
> for this sort of thing, rather than in the executables themselves.
Which doesn't work if you have multiple installations of certain
libraries.
> On a related note: we recently had a linux RPM that tried to
> access /home/david/..., because the packaging was done in that
> directory. It gracefully handled the failure and found the libraries
> elsewhere, though. No problem?
That's what -rpath/-R does, it makes the app look in that path first,
after that it looks in all the other places. At least, AFAICT.
> Well, IIRC, someone using automounted home directories had a problem.
>
> It could have been worse: imagine that a nefarious David on the same
> machine noticed the broken embedded rpath info in the svn executable
> and decided to put doctored versions of the shared libraries in his
> home directory?
Well, that's the packagers problem, isn't it? One would expect people
to check these things becfore shipping.
Anyway, Ben and I think the fix could be documentation. Tell the user
he should set his LDFLAGS to -R/path/to/libs if he needs to.
This is potentially a discussion without end...
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Sep 12 20:48:37 2003