On Thu, 2004-01-15 at 15:51, Buddy Burden wrote:
> Folks,
>
> Using John Peacock's advice, I tried this:
>
> cd /usr/local
> sudo mkdir subversion
> cd subversion
> sudo mkdir db4 apache svn-0.35.1
> sudo ln -s svn-035.1 svn
>
> cd ~/src/db-4.2.52/build_unix
> ../dist/configure --prefix=/usr/local/subversion/db4
> make
> sudo make docdir=/usr/local/subversion/db4/db install
>
> cd ~/src/httpd-2.0.48
> ./configure --prefix=/usr/local/subversion/apache --enable-so --enable-dav --with-berkeley-db=/usr/local/subversion/db4
> make
> sudo make install
>
> cd ~/src/subversion-0.35.1
> ./configure --prefix=/usr/local/subversion/svn-0.35.1 --with-berkeley-db=/usr/local/subversion/db4
It's this last step that's going wrong. You don't need to tell
subversion where berkeley-db is, just tell it where apache is.
The main idea here is this: apache's apr-util is the "keeper" of all
BDB compile information. Both apache and svn ask apr-util for BDB
flags. This guarantees that apache and svn are always using the same
version of BDB (which used to a big problem.)
So the general algorithm is:
1. install BDB
2. make sure apache and its apr-util build against it
(--with-berkeley-db, and possibly including the library in
/etc/ld.so.conf)
3. run subversion's configure with NO MENTION of bdb. If it finds the
installed apache, it will get all BDB info from the apr-util.
So in your recipe above, I would verify that httpd and its apr-util
*really* are linking against the BDB you want. If not, check your
ld.so.conf is correct.
Once that's done, you need to tell subversion's configure where to find
apache's apr and apr-util live (--with-apr and --with-apr-util).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 15 23:21:24 2004