On Thu, Jan 22, 2004 at 12:57:38AM +0000, Philip Martin wrote:
> Yes, I had 1.3.16 built from a tarball. It identifies itself as
> /usr/local/swig-1.3.16/bin/swig -version
> SWIG Version 1.3.16u-20021212-0013
> Copyright (c) 1995-1998
> University of Utah and the Regents of the University of California
> Copyright (c) 1998-2002
> University of Chicago
> Compiled with CC
> and the configure code cannot handle that version number.
Okay. Patch is up to fix this on issue #1690. epg is looking at it and
it should be committed soon.
> I don't build the perl bindings as I only have 5.6.1 installed (I note
> that Subversion's configure doesn't appear to detect that my perl is
> too old).
Humm maybe we should do something about that.
> I have verified that 1.3.16 doesn't work with the Python bindings
> either, it doesn't have SWIG_Python_ConvertPtr, so I guess something
> newer is required for python as well.
Prior to 1.3.20 it would have been SWIG_ConvertPtr. And 1.3.16 does
[breser@occipital .libs]$ strings libswigpy.so | grep ConvertPtr
So it's possible that the Python bindings will work with 1.3.16. I just
thought it was overly complicated to require 1.3.19 or newer for the
perl bindings while requiring 1.3.16, 1.3.17 or 1.3.19 or newer for the
> checking for Tcl library... not found
> checking for python... python
> checking for Python prefix... /usr
> checking for Python exec-prefix... /usr
> checking for Python version... python2.1
> checking for Python header files... -I/usr/include/python2.1 -I/usr/lib/python2.1/config
> checking for Python library... /usr/lib/python2.1/config
> checking for perl... perl
> Looks OK to me, but it doesn't produce libswigpy.so only swigrun.i. I
> looked at Swig's "configure --help" but there was on obvious option to
> enable libswigpy. The installed swig executable has a -python option.
> The process of converting swigrun.i into a shared library is something
> swig -python -o swigpy.c swigrun.i
> libtool --mode=compile gcc -o swigpy.lo -c swigpy.c
> libtool --mode=link gcc -rpath /some/path -o libswigpy.la swigpy.lo
> libtool --mode=install install-sh -c libswigpy.la /some/path/libswigpy.la
> I know very little about swig. Is this a Swig library that I am
> supposed to build and install with Swig? Or is it an application
> library that Subversion should build and install with the other
> Subversion libraries?
> The first thing I tried was to create and install libswigpy.so, that
> allowed me to run "make swig-py" and "install swig-py". Next I
> removed -c from RUN_SWIG_PY and -lswigpy from the link command (which
> I did by editing Makefile and build-outputs.mk) and that also worked.
> Either way when I try to run svnlook.py I get
> Traceback (most recent call last):
> File "/home/pm/sw/subversion/svn/tools/examples/svnlook.py", line 23, in ?
> from svn import core, fs, delta, repos
> File "/usr/local/subversion/lib/svn-python/svn/core.py", line 21, in ?
> from libsvn.core import *
> File "/usr/local/subversion/lib/svn-python/libsvn/core.py", line 5, in ?
> import _core
> ImportError: /usr/local/subversion/lib/libsvn_swig_py-1.so.0: undefined symbol: SWIG_TypeQuery
Did you do:
That's necessary to get the runtime libs.
Ben Reser <email@example.com>
"Conscience is the inner voice which warns us somebody may be looking."
- H.L. Mencken
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Jan 22 02:13:26 2004