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

Re: Support for BDB in RPM's

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2005-04-27 14:14:29 CEST

David Summers <david@summersoft.fay.ar.us> writes:

> On Tue, 26 Apr 2005, Philip Martin wrote:
>>
>> $ make EXTRA_CFLAGS=-I/some/path EXTRA_LDFLAGS="-L/some/path -lsome-lib"
>>
>> Alternatively, you may be able to do it by editing the Makefile (or
>> perhaps Makefile.in) and changing things like SVN_DB_LIBS and CFLAGS.
>
> Nope, that didn't work. :-( It compiled and it has the lib-4.2
> library listed but the db files are version 4.1.

As far as I know it should work. You have to arrange your header
files and your -I directives so that the Subversion compile picks up
the 4.2 bdb header files and not the 4.1 header files, i.e. you have
to arrange the search order so that 4.2 comes *first*. The compile
will still work if you get that wrong, but it won't use the bdb 4.2
symbols.

Try running nm on libsvn_fs_base-1.so and you should see undefined
references to the 4.2 symbols rather than the 4.1 symbols:

$ nm subversion/libsvn_fs_base/.libs/libsvn_fs_base-1.so | grep db_cre
         U db_create_4002

If you got your compile command wrong you will see references to 4.1
symbols instead of the 4.2 symbols.

>> Or you might want to try hacking the m4 stuff in order to make
>> configure do what you want, and then get that patch accepted on the
>> trunk.
>
> I'll play around some more with the m4 stuff, if I can just get it to
> NOT link in the BDB 4.1 stuff then I *may* have a fighting chance.

That won't work, apr-util has references to the 4.1 symbols so you
need to link 4.1.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Apr 27 14:16:02 2005

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

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