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

Re: Configuring Subversion with Berkeley DB Error: configure: error: Berkeley DB 4.0.14 or 5.x wasn't found

From: Branko Čibej <brane_at_wandisco.com>
Date: Thu, 12 Feb 2015 18:45:57 +0100

On 12.02.2015 17:41, kay wrote:
> Brane,
> Which include are you referring to here. Below is what I used for the
> ./configure step:
>
> ./configure --prefix=/dhhs1t/3rdparty/tools/svn --with-apr=/usr/local/apr/
> --with-apr-util=/usr/local/apr/
> --with-berkeley-db=/usr/local/BerkeleyDB.5.3/include/db.h:/usr/local/BerkeleyDB.5.3/include:/usr/local/BerkeleyDB.5.3/lib:db-5.3
> --with-serf=yes --with-apxs=/dhhs1t/3rdparty/tools/apache/bin/apxs
> --with-sqlite=/dhhs1t/3rdparty/tools/svn/subversion-1.8.11/sqlite-amalgamation/sqlite3.c
> --enable-maintainer-mode.
>
> The include that I noticed there is that of BDB. Just wanted to be sure that
> is what you are referring to.

I'm talking about the include path used by the compiler. See your 'make'
logs; this is the first line:

/bin/bash /dhhs1t/3rdparty/tools/svn/subversion-1.8.11/libtool --tag=CC
--silent --mode=compile gcc -std=c89 -DSOLARIS2=10
-D_POSIX_PTHREAD_SEMANTICS -D_REENTRANT -D_LARGEFILE64_SOURCE -g -O2 -g
-O2 -I./subversion/include -I./subversion -I/usr/local/apr/include/apr-1
-I/usr/local/apr/include/apr-1 -I/usr/local/BerkeleyDB.5.3/include
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/gnome-keyring-1 -I/usr/local/include/serf-1
-I/dhhs1t/3rdparty/tools/svn/subversion-1.8.11/sqlite-amalgamation -o
subversion/libsvn_delta/cancel.lo -c subversion/libsvn_delta/cancel.c

All those -I options define the include path, which the compiler uses in
addition to any defaults (usually -I/usr/include but there may be
others; it's compiler- and platform-specific).

-- Brane

P.S.: I thought this was a developers' list
Received on 2015-02-12 18:48:00 CET

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.