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

subversion swig-python

From: Jon Scott Stevens <jon_at_latchkey.com>
Date: 2005-02-02 08:00:36 CET

Using a freshly compiled and installed svn 1.1.3 with the swig bindings
from 1.3.21 (./configure;make;make install).

Except for some ld warnings about libiconv/libintl being multiply
defined (I have it installed via fink in /sw) everything seems to have
gone ok with the subversion build and I have a working svn binary and
apache module.

With the swig build, I'm seeing stuff like this:

*** Warning: linker path does not have real file for library -lswigpy.
*** I have the capability to make that library automatically link in
when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with libswigpy but no candidates were found. (...for file magic
test)

*** Warning: linker path does not have real file for library -lintl.
*** I have the capability to make that library automatically link in
when
*** you link to this library. But I can only do this if you have a
*** shared version of the library, which you do not appear to have
*** because I did check the linker path looking for a file starting
*** with libintl and none of the candidates passed a file format test
*** using a file magic. Last file checked: /usr/lib/libSystem.B.dylib

*** Warning: libtool could not satisfy all declared inter-library
*** dependencies of module _core. Therefore, libtool will create
*** a static module, that should work as long as the dlopening
*** application is linked with the -dlopen flag.

Although, the build/install seems to work just fine.

Finally, this is the error I'm getting when I'm trying to test the
swig-py installation to see if it works...

[25][ /usr/local/src/subversion/subversion-1.1.3 ]# python
Python 2.4 (#1, Jan 18 2005, 19:18:27)
[GCC 3.3 20030304 (Apple Computer, Inc. build 1671)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
>>> import sys
>>> print sys.path
['', '/usr/local/lib/svn-python',
'/Library/Frameworks/Python.framework/Versions/2.4/lib/python24.zip',
'/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4',
'/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/plat-
darwin',
'/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/plat-
mac',
'/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/plat-
mac/lib-scriptpackages',
'/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/lib-
tk',
'/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/lib-
dynload',
'/Library/Frameworks/Python.framework/Versions/2.4/lib/python2.4/site-
packages']
>>> import svn.repos
Traceback (most recent call last):
   File "<stdin>", line 1, in ?
   File "/usr/local/lib/svn-python/svn/repos.py", line 19, in ?
     import svn.fs
   File "/usr/local/lib/svn-python/svn/fs.py", line 28, in ?
     import libsvn.fs
   File "/usr/local/lib/svn-python/libsvn/fs.py", line 5, in ?
     import _fs
ImportError: No module named _fs

No /usr/local/lib/svn-python/libsvn/_fs.py exists or is ever created,
but a _fs.a and _fs.la exists.

OSX 10.3.7
Python 2.4
SWIG 1.3.21
Subversion 1.1.3

My build script...

#!/bin/sh

APP=subversion
VER=1.1.3
LDFLAGS="-multiply_defined suppress"
export LDFLAGS

if [ ! -e $APP-$VER ] ; then
tar -xzf $APP-$VER.tar.gz
fi

cd $APP-$VER
./configure \
         --with-apxs=/usr/sbin/apxs \
         --with-berkeley-db=/sw \
         --with-swig \
         --enable-swig-bindings=python

make
make install
make swig-py
make install-swig-py

What's up doc?

jon

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Feb 2 08:03:12 2005

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

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