apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject Re: [MAINTAINER] devel/apr-gdbm-db42: apr-util 1.3.7 breaks dbd support
Date Tue, 09 Jun 2009 05:48:13 GMT
Bojan Smojver wrote:
> On Mon, 2009-06-08 at 23:16 -0400, Philip M. Gollucci wrote:
>> -ldb* is never added to APRUTIL_EXPORT_LIBS so that apu-config.in ->
>> apu-1-config can report on whats there using (i.e. from subversion)
> 
> Probably the result of moving the DBM (not DBD) to DSO.

And actually; not the job of apr, unless this is a static build?  You'll
note that the library is linked to the berkeley stub.  E.g. (on linux here)

$ ldd lib/apr-util-1/apr_dbm_db.so
        linux-vdso.so.1 =>  (0x00007fff8c3fe000)
        libdb-4.7.so => /lib64/libdb-4.7.so (0x00007faf83e75000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007faf83c59000)
        libc.so.6 => /lib64/libc.so.6 (0x00007faf838e6000)
        /lib64/ld-linux-x86-64.so.2 (0x0000003a3b000000)

Trivial to disable the dso feature for static libraries, if that is the
problem.  Simply --disable-util-dso

If the problem is that the user wants apr-util db + specific BerkeleyDB
features, that isn't what APR exists to provide.  The autoconf tests
may be liberally borrowed from, obviously, as they are Apache licensed :)

Mime
View raw message