Lev Serebryakov wrote:
>>> Is it known problem, that any bindings, which uses SWIG, can not
>>> be built with latest SWIG?
>>> Will this problem be fixed in 1.2.1?
You're rather overstating the problem. Python and Ruby bindings build fine
for me. There is a minor issue with the Perl bindings, but it seems to have
a trivial fix. It definitely won't be fixed in 1.2.1, since 1.2.1 is already
rolled and awaiting final approval for release. Assuming it doesn't turn out
to be less trivial than I thought, it should be fixed in 1.2.2, though.
>> I don't understand, the CHANGES entry for svn 1.1.4 says:
>> * add SWIG 1.3.24 and .25 compatibility (r12551, r12717-9, r12722,
>> r13504)
>> So, what's going on here?
I think .25 wasn't released at the time. We were compatible with .25-dev,
but I guess something changed in swig before the release.
> I see what I see: with swith-1.3.23 everything is Ok,
Umm, really? We never did, do not, and never will officially support swig
1.3.23.
> with swig-1.3.25 I get error messages:
>
> For python:
>
> /work/a/ports/devel/subversion-python/work/subversion-1.2.0/subversion/bindings/swig/python/libsvn_swig_py/swigutil_py.c
> In file included from
> /work/a/ports/devel/subversion-python/work/subversion-1.2.0/subversion/bindings/swig/python/libsvn_swig_py/swigutil_py.c:44:
> /usr/local/share/swig/1.3.25/runtime.swg:28: macro `SWIG_GetModule' used
> without args /usr/local/share/swig/1.3.25/runtime.swg:34: macro
> `SWIG_GetModule' used without args
Curious. WJFFM.
> And for perl:
>
...
> core.c:1139: error: syntax error before "apr_pool_t"
> *** Error code 1
Yes, reproduced.
Workaround:
Change the two occurrences of "SWIGEXPORT(foobar)" to "SWIGEXPORT foobar" in
subversion/bindings/swig/core.i
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jul 4 01:13:00 2005