python/svn issues....

[David M. Cooke]

"bruce" <bedouglas at earthlink.net> writes:

> hi...
>
> in trying to get viewcvs up/running, i tried to do the following:
>
> [root at lserver2 viewcvs-0.9.2]# python
> Python 2.3.3 (#1, May  7 2004, 10:31:40)
> [GCC 3.3.3 20040412 (Red Hat Linux 3.3.3-7)] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>>>> import svn.repos
> Traceback (most recent call last):
>   File "<stdin>", line 1, in ?
>   File
> "/dar/tmp/subversion-1.1.4-0.1.1.fc2.rf-root/usr/lib/python2.3/site-packages
> /svn/repos.py", line 19, in ?
>   File
> "/dar/tmp/subversion-1.1.4-0.1.1.fc2.rf-root/usr/lib/python2.3/site-packages
> /svn/fs.py", line 28, in ?
>   File
> "/dar/tmp/subversion-1.1.4-0.1.1.fc2.rf-root/usr/lib/python2.3/site-packages
> /libsvn/fs.py", line 4, in ?
> ImportError: /usr/lib/libsvn_fs_base-1.so.0: undefined symbol: db_create

This looks like a problem when Subversion was built: this library was
not linked against the Berkeley DB libraries.

You can check what's linked using ldd, and see the unresolved symbols
with ldd -r. For instance, on my AMD64 Debian system,

$ ldd -r /usr/lib/libsvn_fs_base-1.so.0
        libsvn_delta-1.so.0 => /usr/lib/libsvn_delta-1.so.0 (0x0000002a95696000)
        libsvn_subr-1.so.0 => /usr/lib/libsvn_subr-1.so.0 (0x0000002a9579f000)
        libaprutil-0.so.0 => /usr/lib/libaprutil-0.so.0 (0x0000002a958c8000)
        libldap.so.2 => /usr/lib/libldap.so.2 (0x0000002a959e0000)
        liblber.so.2 => /usr/lib/liblber.so.2 (0x0000002a95b19000)
        libdb-4.2.so => /usr/lib/libdb-4.2.so (0x0000002a95c27000)
        libexpat.so.1 => /usr/lib/libexpat.so.1 (0x0000002a95e05000)
        libapr-0.so.0 => /usr/lib/libapr-0.so.0 (0x0000002a95f29000)
        librt.so.1 => /lib/librt.so.1 (0x0000002a9604e000)
        libm.so.6 => /lib/libm.so.6 (0x0000002a96155000)
        libnsl.so.1 => /lib/libnsl.so.1 (0x0000002a962dc000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x0000002a963f2000)
        libc.so.6 => /lib/libc.so.6 (0x0000002a96506000)
        libdl.so.2 => /lib/libdl.so.2 (0x0000002a96746000)
        libcrypt.so.1 => /lib/libcrypt.so.1 (0x0000002a96849000)
        libresolv.so.2 => /lib/libresolv.so.2 (0x0000002a9697c000)
        libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x0000002a96a91000)
        libgnutls.so.11 => /usr/lib/libgnutls.so.11 (0x0000002a96ba8000)
        /lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x000000552aaaa000)
        libtasn1.so.2 => /usr/lib/libtasn1.so.2 (0x0000002a96d1b000)
        libgcrypt.so.11 => /usr/lib/libgcrypt.so.11 (0x0000002a96e2b000)
        libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x0000002a96f77000)
        libz.so.1 => /usr/lib/libz.so.1 (0x0000002a9707b000)

If it doesn't look like that, then I'd say your Subversion package was
built badly. You may also want to run ldd on your svn binary, to see what
libraries it pulls in.

-- 
|>|\/|<
/--------------------------------------------------------------------------\
|David M. Cooke
|cookedm(at)physics(dot)mcmaster(dot)ca