Re: trouble installing swig bindings

Greg Stein wrote:
> try:
>
> $ rm subversion/bindings/swig/python/*.c
> $ make install-swig-py # note that gmake shouldn't be necessary
>
> It may be that the bindings did not get properly rebuilt at some point.
> There are still some nigglies in the build system for the bindings.

Hm. This didn't help. I've tried this on 0.20.1 before I wrote the original
letter, and I just tried this on r5610 with SWIG-1.3.19. Same results.

Maybe there are some known issues with swig bindings on FreeBSD?

>>SWIG is 1.3.16 . At first I installed 1.3.19, but ./configure prints a
>>warning that 1.3.16 is required and then gmake swig-py breaks not finding
>> Python.h and libtool errors (like ' unrecognized option `-rpath'') if I
>>define EXTRA_CFLAGS to point to its location.
>
>
> The configure script was updated the other day to allow 1.3.19. That is in
> the SVN trunk, and will appear in the 0.21 release.
>
> Regarding Python.h -- make sure that you have the development stuff
> installed for Python. (I'm not sure how it works on FreeBSD, but under
> RedHat, I'd install the python-devel RPM).

That's a FreeBSD 4.6.2, and I hand-installed Python there. The errors I
mentioned (concerning Python.h) were most probably due to ./configure not
setting up some paths somewhere while not disabling swig-* targets altogether.

-- 
./lxnt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org