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

Re: configure.in question

From: Greg Stein <gstein_at_lyra.org>
Date: 2001-03-30 00:01:05 CEST

On Thu, Mar 29, 2001 at 09:17:16AM -0600, Ben Collins-Sussman wrote:
> Can somebody explain this configure.in section to me?
> I don't get it. Don't we want to link ra_dav if $enable_shared is
> YES?

No. If we build a shared library, then we will dynamically load it, rather
than link with it. If we only build a static library, *then* it gets linked

We have three ways to build, with suboptions on a couple:

1) static only. link against libsvn_ra_*
2) shared only.
   a) link against libsvn_ra_*.so
   b) dynload libsvn_ra_*
3) static and shared.
   a) link against libsvn_ra_*.so
   b) link against libsvn_ra_*.a
   c) dynload libsvn_ra_*

As I mentioned way back when I set this up, our configure process will do
(1) or (2b) or (3c). We could set things up to optionally link against the
libs, as in (2a) and (3a). libtool won't give us (3b) without more work.

> I've built and installed the shared-lib 'dav-aware' svn binary on
> two different systems now, and both times I had to (locally) change
> this test to "yes". Otherwise, the binary doesn't recognize the http:
> schema, because SVN_LIBSVN_CLIENT_LINKS_RA_DAV never gets defined in
> ra_loader.c. (Greg?)

That is not *supposed* to be defined when shared libs are being used.

Do your "make install" so that the libs go into /usr/local/lib. Then make
sure that you do an "ldconfig" so that the OS knows where they are and can
load them. On my linux system, I had to add two lines to my /etc/ld.so.conf


If you want to ask for a link-shared option, then that is one thing. But the
current system works as designed. (i.e. ask for additional features cuz its
works as planned today :-)


Greg Stein, http://www.lyra.org/
Received on Sat Oct 21 14:36:26 2006

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