I used SWIG-1.3.17, I had no luck with 1.3.16, new could work but I didn't
try it. You also have to install the python-devel package or it can't find
out how to compile python extensions. The rest is like in the
documentation, you should read all INSTALL files, for example the one in
subversion/bindings/swig.
Florian
On 31 Mar 2003 00:52:21 +0200, Tomek Meka <tmeka@gmx.net> wrote:
> On Mon, 2003-03-31 at 00:29, Florian Schulze wrote:
>> Ok, I got them to compile, it was my fault.
> How did you do it? I get the same error, and have no idea, what to do. I
> also compile svn without any errors, but after executing make swig-py I
> get:
> [tomek@dhcppc0 subversion-0.20.1]$ make swig-py
> /bin/sh /home/tomek/sources/subversion-0.20.1/libtool --silent
> --mode=compile -I/home/tomek/sources/subversion-
> 0.20.1/subversion/bindings/swig
> -I/home/tomek/sources/subversion-0.20.1/subversion/include
> -I/home/tomek/sources/subversion-0.20.1/apr/include -prefer-pic -c -o
> subversion/bindings/swig/python/svn_client.lo
> subversion/bindings/swig/python/svn_client.c
> libtool: unrecognized option
> `-I/home/tomek/sources/subversion-0.20.1/subversion/bindings/swig'
> Try `libtool --help' for more information.
> make: *** [subversion/bindings/swig/python/svn_client.lo] Error 1
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Mar 31 11:08:45 2003