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

Re: neon/serf selection

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2006-07-11 01:20:51 CEST

Branko Čibej <brane@xbc.nu> writes:

> Philip Martin wrote:
>> I've noticed that my neon-using svn client attempts to load the
>> ra_serf library dynamically. Since I'm using Linux I have APR_HAS_DSO
>> set but I don't use --enable-dso so libsvn_ra is explicitly linked to
>> libsvn_ra_dav. I don't have serf installed and I don't build ra_serf.
>> Despite this Subversion's DSO code attempts to load ra_serf at
>> runtime. Is it supposed to work this way?
> It's a "feature". Same happens with ra_dav if I don't build neon, and
> the dam' thing actually errors out. That's something I don't actually
> understand, given that the ra_loader is suppoesd to ignore library load
> errors.

It means one cannot reliably run the regression tests unless one knows
what is installed. The DSO code looks in the install directory for
the "missing" library even when run from the build directory, and if a
library is found in the install dir there is no guarantee that it is
compatible with the build (that might explain your errors). Even if
the installed library is ABI compatible having two modules handling
the same scheme doesn't seem sensible, I suppose one simply overrrides
the other.

Does anyone think the current behaviour is correct?

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 11 01:21:17 2006

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.