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

Re: check-swig-pl requires berkeley db with svn-1.14.0

From: Daniel Shahaf <d.s_at_daniel.shahaf.name>
Date: Tue, 2 Jun 2020 01:09:41 +0000

Karl Berry wrote on Mon, 01 Jun 2020 15:01 -0600:
> With svn-1.14.0, if --without-berkeley-db is given to configure, and
> --with-swig is given, make swig-pl succeeds, but check-swig-pl fails
> with:

> When --without-berkeley-db is omitted, all tests succeed.

No idea.

It's a shot in the dark, but try configuring with a dummy --prefix and
then running «make install install-swig-pl» before «make check-swig-pl».
Yes, that's backwards, but it's required on some platforms due to
dynamic linker behaviour.

> It would be nice if the configure script bailed out in this
> configuration instead of leaving it for a painful Perl message after
> building everything.

We're well aware of "If you have to fail, fail fast", but in this case
we shouldn't fail at all. Building swig-pl without bdb is supported;
it should succeed.

Moreover, passing --with-swig doesn't imply the Perl bindings are to be
built, so does not merit failing configure even if there's no Perl
installation on the system at all. (For that, see the soon-to-be-added-
to-trunk --with-swig-perl[=/path/to/bin/perl] configure option.)

Note that swig isn't required at all when building from a tarball.

> Assuming it's intentional that BDB is required. I'm not sure if it was
> in previous releases.

BDB hasn't been a mandatory dependency since 1.2.x (sic); will not
become a mandatory dependency again due to Apache Software Foundation
licensing policies; and if it does become a mandatory dependency again,
that will be highlighted in the release notes.


Received on 2020-06-02 03:09:56 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.