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

Re: The *.so files

From: Joe Orton <joe_at_manyfish.co.uk>
Date: 2002-11-06 23:52:23 CET

On Wed, Nov 06, 2002 at 02:16:45PM -0800, Greg Stein wrote:
> On Wed, Nov 06, 2002 at 09:22:35PM +0000, Joe Orton wrote:
> > SVN treats ra_dav and ra_local as libraries, but really they are
> > loadable modules - I think this is where the disconnect is happening.
>
> They *can* be loadable modules. Normally, we just link them in. But if you
> pass --enable-dso to ./configure, then it will stop linking them in. When
> doing so, however, the DSO loader must be able to find them. I'm not sure
> what the Linux rules are for that. I suspect the paths in ld.so.conf and/or
> LD_LIBRARY_PATH.

Ah, okay, I'd thought this was the default for shared builds.

It looks like build.conf specifies $(NEON_LIBS) as a dependency of the
svn binary, which seems odd. That makes putting the ra_dav module in a
separate package a little pointless, since the neon dependency isn't
isolated.

> > The loadable modules should really go in %{_libdir}/subversion/*.so,
> > though you'd probably need to modify the ra loader to look in the right
> > place.
>
> Yah, sounds about right. Any ideas on how to get the system to "look in the
> right place" ? It it simply a matter of passing an absolute path to the
> loader?

Yes, exactly; otherwise you have to mess with LD_LIBRARY_PATH or
ld.so.conf etc.

joe

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Nov 6 23:53: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.