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

Re: Failing tests Darwin/Debian

From: David James <djames_at_collab.net>
Date: 2006-05-27 20:10:57 CEST

On 5/27/06, Erik Huelsmann <ehuels@gmail.com> wrote:
> Trying to set up a buildbot slave on my system, I had failing tests
> (ra-local-test and svnsync_tests.py).
> The problem looked like the system was linking to the wrong dynamic libs.
> Knowing Debian libtool can cause problems like that when testing
> non-installed libs, I changed libtool to vanilla 1.5.22 (and later
> also to 1.5.20). This didn't solve my test problems.

I had a similar problem building Subversion on Ubuntu. I couldn't
build trunk Subversion because libtool linked to the wrong libs.
Installing a vanilla version of libtool fixed the problem. But that's
just me -- every system is different. Did you remember to re-run
autogen.sh && ./configure ?

> [..]
> path = subversion/svnsync
> -libs = libsvn_ra libsvn_delta libsvn_subr apr
> +libs = libsvn_subr libsvn_delta libsvn_ra apr
> install = bin

I don't completely understand what you're doing, but it looks like
you're reordering the dependencies so that the build system will build
them in the correct order. If you have to do this, it's likely because
we've forgotten to list some essential dependencies somewhere else in
the build system.

In your case, it looks like patching libsvn_ra to depend on
libsvn_delta will fix your problem. I figured this out by looking at
libsvn_ra-1.la, and noticing that it contains a reference to
libsvn_delta, but then also noticing that libsvn_ra does not depend on
libsvn_delta in build.conf.

> path = subversion/tests/libsvn_ra_local
> sources = ra-local-test.c
> install = test
> -libs = libsvn_test libsvn_ra_local libsvn_ra
> - libsvn_fs libsvn_delta libsvn_subr
> - aprutil apriconv apr
> +libs = libsvn_subr libsvn_delta libsvn_fs libsvn_test
> + libsvn_ra_local libsvn_ra aprutil apriconv apr

The same rule applies here. You can use the same detective techniques
to find out the true dependencies of each module. In general, if you
find that listing module "y" after module "x" works, but listing it
the other way does not, you can bet that y depends on x.

Hope this helps,


David James -- http://www.cs.toronto.edu/~james
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat May 27 20:11:22 2006

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