You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Pete Gonzalez <pg...@bluel.com> on 2004/01/15 02:14:50 UTC
Berkeley DB compatibility problems
I had problems getting Subversion to compile on a Debian server and
a RedHat server, both of which were lacking the db-4.2 package.
For reference, here's how I solved it:
1. Compile and install db-4.2.52.tar.gz
2. For a non-root installation, add this line to ~/.bash_profile:
export LD_PRELOAD=/home/me/local/BerkeleyDB.4.2/lib/libdb.so
This tells the configure script where to find the db-4.2 libraries.
For a root install, I instead added "/usr/local/BerkeleyDB.4.2/lib"
to /etc/ld.so.conf and re-ran ldconfig.
3. I downloaded apr-util-APU_0_9_BRANCH_20031230052737.tar.gz and
copied the "configure.in" and "build/dbm.m4" files from it,
which was suggested here:
http://www.contactor.se/~dast/svn/archive-2003-12/0312.shtml
(Without changes #2 and #3, the ./configure command would fail.)
4. I ran configure (these options are for the non-root install):
./configure --prefix=/home/me/local/ \
--with-berkeley-db=/home/me/local/BerkeleyDB.4.2/lib/ \
--with-dbm=db42 --with-ssl\
--enable-maintainer-mode --disable-mod-activation
5. Ran "make" and "make install". For non-root install, I had
to first edit the Makefile to remove "install-mods-shared",
since otherwise it tries to copy files into an Apache folder.
I'm not sure why other people haven't encountered the problems
above, but maybe these notes will be useful to someone else.
Cheers,
-Pete
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Berkeley DB compatibility problems
Posted by Pete Gonzalez <pg...@bluel.com>.
At 05:15 AM 1/15/2004, you wrote:
>Can you please run:
>
>ldd /path/to/bin/svn
>ldd /path/to/lib/libsvn_fs-1.so.0.0.0
>ldd /path/to/lib/libsvn_swig_py-1.so.0.0.0
>
>and send the output of these commands to me?
See below. Note that libsvn_swig_py is not installed.
Also, I failed to mention in my posting that I was building
version 0.35.1 -- I haven't upgraded yet because TortoiseSVN is
still using that one.
Cheers,
-Pete
______________
bash# uname -a
Linux emmet 2.4.23 #1 Mon Dec 1 19:00:59 EST 2003 i686 unknown
bash# cat /etc/debian_version
3.0
bash# svn --version
svn, version 0.35.1 (r8050)
compiled Dec 31 2003, 05:41:41
Copyright (C) 2000-2003 CollabNet.
Subversion is open source software, see http://subversion.tigris.org/
The following repository access (RA) modules are available:
* ra_dav : Module for accessing a repository via WebDAV (DeltaV) protocol.
- handles 'http' schema
- handles 'https' schema
* ra_local : Module for accessing a repository on local disk.
- handles 'file' schema
* ra_svn : Module for accessing a repository using the svn network protocol.
- handles 'svn' schema
bash# ldd /usr/local/bin/svn
libsvn_client-1.so.0 => /usr/local/lib/libsvn_client-1.so.0
(0x40014000)
libsvn_wc-1.so.0 => /usr/local/lib/libsvn_wc-1.so.0 (0x40036000)
libsvn_ra-1.so.0 => /usr/local/lib/libsvn_ra-1.so.0 (0x4005e000)
libsvn_diff-1.so.0 => /usr/local/lib/libsvn_diff-1.so.0 (0x40061000)
libsvn_ra_local-1.so.0 => /usr/local/lib/libsvn_ra_local-1.so.0
(0x40068000)
libsvn_repos-1.so.0 => /usr/local/lib/libsvn_repos-1.so.0 (0x4006d000)
libsvn_fs-1.so.0 => /usr/local/lib/libsvn_fs-1.so.0 (0x40083000)
libsvn_ra_dav-1.so.0 => /usr/local/lib/libsvn_ra_dav-1.so.0
(0x400a8000)
libsvn_ra_svn-1.so.0 => /usr/local/lib/libsvn_ra_svn-1.so.0
(0x400bd000)
libsvn_delta-1.so.0 => /usr/local/lib/libsvn_delta-1.so.0 (0x400cd000)
libsvn_subr-1.so.0 => /usr/local/lib/libsvn_subr-1.so.0 (0x400d6000)
libaprutil-0.so.0 => /usr/local/apr/lib/libaprutil-0.so.0 (0x400fc000)
libgdbm.so.1 => /usr/lib/libgdbm.so.1 (0x40114000)
libdb-4.2.so => /usr/local/BerkeleyDB.4.2/lib/libdb-4.2.so
(0x4011a000)
libapr-0.so.0 => /usr/local/apr/lib/libapr-0.so.0 (0x401c4000)
librt.so.1 => /lib/librt.so.1 (0x401e3000)
libm.so.6 => /lib/libm.so.6 (0x401f4000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x40215000)
libnsl.so.1 => /lib/libnsl.so.1 (0x40242000)
libdl.so.2 => /lib/libdl.so.2 (0x40256000)
libneon.so.24 => /usr/local/lib/libneon.so.24 (0x40259000)
libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x40272000)
libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4029f000)
libz.so.1 => /usr/lib/libz.so.1 (0x40360000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x4036e000)
libpthread.so.0 => /lib/libpthread.so.0 (0x4038f000)
libc.so.6 => /lib/libc.so.6 (0x403a3000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
bash# ldd /usr/local/lib/libsvn_fs-1.so.0.0.0
libsvn_delta-1.so.0 => /usr/local/lib/libsvn_delta-1.so.0 (0x40025000)
libsvn_subr-1.so.0 => /usr/local/lib/libsvn_subr-1.so.0 (0x4002f000)
libaprutil-0.so.0 => /usr/local/apr/lib/libaprutil-0.so.0 (0x40055000)
libgdbm.so.1 => /usr/lib/libgdbm.so.1 (0x4006d000)
libdb-4.2.so => /usr/local/BerkeleyDB.4.2/lib/libdb-4.2.so
(0x40073000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0x4011d000)
libapr-0.so.0 => /usr/local/apr/lib/libapr-0.so.0 (0x4013e000)
librt.so.1 => /lib/librt.so.1 (0x4015c000)
libm.so.6 => /lib/libm.so.6 (0x4016d000)
libcrypt.so.1 => /lib/libcrypt.so.1 (0x4018f000)
libnsl.so.1 => /lib/libnsl.so.1 (0x401bc000)
libdl.so.2 => /lib/libdl.so.2 (0x401d0000)
libc.so.6 => /lib/libc.so.6 (0x401d3000)
libpthread.so.0 => /lib/libpthread.so.0 (0x402f0000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x80000000)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Berkeley DB compatibility problems
Posted by Mukund <mu...@tessna.com>.
Pete
Can you please run:
ldd /path/to/bin/svn
ldd /path/to/lib/libsvn_fs-1.so.0.0.0
ldd /path/to/lib/libsvn_swig_py-1.so.0.0.0
and send the output of these commands to me?
Thanks!
Mukund
On Wed, Jan 14, 2004 at 09:14:50PM -0500, Pete Gonzalez wrote:
> I had problems getting Subversion to compile on a Debian server and
> a RedHat server, both of which were lacking the db-4.2 package.
>
> For reference, here's how I solved it:
>
> 1. Compile and install db-4.2.52.tar.gz
>
> 2. For a non-root installation, add this line to ~/.bash_profile:
>
> export LD_PRELOAD=/home/me/local/BerkeleyDB.4.2/lib/libdb.so
>
> This tells the configure script where to find the db-4.2 libraries.
> For a root install, I instead added "/usr/local/BerkeleyDB.4.2/lib"
> to /etc/ld.so.conf and re-ran ldconfig.
>
> 3. I downloaded apr-util-APU_0_9_BRANCH_20031230052737.tar.gz and
> copied the "configure.in" and "build/dbm.m4" files from it,
> which was suggested here:
>
> http://www.contactor.se/~dast/svn/archive-2003-12/0312.shtml
>
> (Without changes #2 and #3, the ./configure command would fail.)
>
> 4. I ran configure (these options are for the non-root install):
>
> ./configure --prefix=/home/me/local/ \
> --with-berkeley-db=/home/me/local/BerkeleyDB.4.2/lib/ \
> --with-dbm=db42 --with-ssl\
> --enable-maintainer-mode --disable-mod-activation
>
> 5. Ran "make" and "make install". For non-root install, I had
> to first edit the Makefile to remove "install-mods-shared",
> since otherwise it tries to copy files into an Apache folder.
>
> I'm not sure why other people haven't encountered the problems
> above, but maybe these notes will be useful to someone else.
>
> Cheers,
> -Pete
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org