Re: problem building with Berkeley DB 4.1.24

Karl Fogel <kfogel@newton.ch.collab.net> writes:

> I'm seeing a problem in apr-util/ when I try to build a shared
> Subversion (including mod_dav_svn) using Berkeley DB 4.1.24. (I've
> had no trouble building with 4.0.14 before now.)
>
> This is on a RedHat 7.0 system, FWIW. Both of these dirs exist:
>
> /usr/local/BerkeleyDB.4.0/
> /usr/local/BerkeleyDB.4.1/
>
> but /etc/ld.so.conf mentions only "/usr/local/BerkeleyDB.4.1/lib/",
> and I re-ran ldconfig. Then I did:
>
> $ ./autogen.sh;
> $ ./configure --enable-maintainer-mode
>
> Various configure spew omitted here (the full output is included at
> the end of this mail), but anyway it did seem to find DB 4.1.24 in the
> expected place. Nevertheless, the build eventually fails with this
> error:
>
> libtool: link: warning: library `/usr/lib/libgdbm.la' was moved.
> libtool: link: warning: library `/usr/lib/libgdbm.la' was moved.
> /home/kfogel/src/subversion/apr-util/.libs/libaprutil-0.so: undefined reference to `dbopen'
> collect2: ld returned 1 exit status
> make: *** [subversion/clients/cmdline/svn] Error 1

I'm building shared Subversion against BDB 4.1.24 these days, although
I am using Apache's installed apr/apr-util rather than ones in the
Subversion tree. So this means that I'm also building Apache against
BDB 4.1.24, and I see that Apache's apr-util links against libgdbm, I
don't remember this being the case when I built against BDB 4.0.14.

Is it possible that you have a broken libgdbm installation, and that
it simply isn't used when you use BDB 4.0.14?

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org