[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: broken libtool on freebsd

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-06-12 16:53:41 CEST

Joe Orton <joe@manyfish.co.uk> writes:

> On Tue, Jun 11, 2002 at 04:46:03PM -0500, Ben Collins-Sussman wrote:
> > Joe Orton <joe@manyfish.co.uk> writes:
> >
> > > If you truss lt-svn, is it opening the libs directly out of
> > > /usr/local/lib first (and not trying anywhere else beforehand)?
> >
> > Nope, according to truss, lt-svn attempts to open each libsvn library
> > in "." first, (i.e. "./libsvn_client.so"). That fails, and then it
> > immediately succeeds in opening the library out of /usr/local/lib/.
> Hmmm, you don't have $LD_LIBRARY_PATH set to /usr/local/lib do you? If
> not I'm out of guesses...

Hm, yeah, I *do* have LD_LIBRARY_PATH set to .:/usr/local/lib. I
think it gets set in my .bash_profile.

Is that environment variable really so strong?

Holy cow. I guess so! I just unset the variable, and now 'ldd
lt-svn' resolves all libraries to ones within my build tree, just as
it should be.

Wow, I just don't get it... I thought the runtime loader always looked
at compile-time 'rpaths' first, before anything else...

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 12 14:40:00 2002

This is an archived mail posted to the Subversion Dev mailing list.