On 5/27/06, David James <djames@collab.net> wrote:
> 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 ?
Yup. I'm using a buildbot config to test it: make extraclean &&
autogen && configure && make.
> > [..]
> > 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.
Reordering, yes.
> 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.
But, you suggest to add a dependency to build.conf, right? I tested
that, but it doesn't work for me, nor for breser...
Would have been nice if it did: way more explicable than the current
situation...
Thanks for the feedback.
bye,
Erik.
Received on Sat May 27 21:06:18 2006