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

Re: Building Apache & mod_dav_svn

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2002-07-22 18:57:44 CEST

Garrett Rooney <rooneg@electricjellyfish.net> writes:

> On Mon, Jul 22, 2002 at 05:42:20PM +0100, Philip Martin wrote:
> > > Hmmm. Before I do a full, dynamic build, I always "clean up" my
> > > system using a shell script (included at the end of this mail).
> >
> > I usually use a dynamic Subversion build but I never "clean up" first,
> > what problems does it solve?
> there used to be issues with your new build getting linked against old
> versions of the libs that you had installed, leading to weird bugs. i
> believe they've been fixed, but karl is probably still paranoid.

I was the original instigator of the paranoia.

It turns out that on freebsd, the LD_LIBRARY_PATH variable takes
precedence over the default runtime-linker search locations, which is
*totally* broken IMO.

I happen to set LD_LIBRARY_PATH=/usr/local/lib in my .bash_profile, so
I would see bizarre behavior: I would compile svn shared, and then
run ldd on '.libs/lt-svn', and see that the runtime-linker was
resolving all libraries references to /usr/local/lib/libsvn_*, instead
of the libraries lying around my source tree, as it should.

It took me a while to figure out that this was a freebsd bug; so in
the meantime, I spread vicious rumors about everyone needing to delete
all of /usr/local/lib/libsvn_* when re-building shared. It's not
true. :-)

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 22 18:59:36 2002

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.