You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Lev Serebryakov <le...@serebryakov.spb.ru> on 2005/07/03 17:29:31 UTC
SWIG 1.3.25: subversion can not be build with it :(
Hello users,
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?
--
Best regards,
Lev mailto:lev@serebryakov.spb.ru
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re[2]: SWIG 1.3.25: subversion can not be build with it :(
Posted by Lev Serebryakov <le...@serebryakov.spb.ru>.
Hello Erik,
Sunday, July 3, 2005, 9:33:24 PM, you wrote:
>> Will this problem be fixed in 1.2.1?
EH> No, substantial changes were made to SWIG between 1.3.21 and 1.3.25
EH> and subversion development has targeted at new core features and fixes
EH> for the moment.
IMHO, it is `fix'. Because many packagein systems (FreeBSD ports, for examle) update their SWIG version and subversion can not be build on such systems. :(
It is very hard to require `old' versions of packages on such systems :(
EH> But, if you are willing to supply patches: they're most welcome!
:) I'll try to provide one.
--
Best regards,
Lev mailto:lev@serebryakov.spb.ru
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: SWIG 1.3.25: subversion can not be build with it :(
Posted by Erik Huelsmann <eh...@gmail.com>.
On 7/3/05, Lev Serebryakov <le...@serebryakov.spb.ru> wrote:
> Hello users,
>
> Is it known problem, that any bindings, which uses SWIG, can not be built with latest SWIG?
Yes, except maybe the Ruby bindings.
> Will this problem be fixed in 1.2.1?
No, substantial changes were made to SWIG between 1.3.21 and 1.3.25
and subversion development has targeted at new core features and fixes
for the moment. But, if you are willing to supply patches: they're
most welcome!
bye,
Erik.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re[4]: SWIG 1.3.25: subversion can not be build with it :(
Posted by Lev Serebryakov <le...@serebryakov.spb.ru>.
Hello Max,
Monday, July 4, 2005, 3:09:43 AM, you wrote:
>> I see what I see: with swith-1.3.23 everything is Ok,
MB> Umm, really? We never did, do not, and never will officially support
MB> swig 1.3.23.
Oh, It is my fault. Previous version I tried was 1.3.21!
>> 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
MB> Curious. WJFFM.
It is cut'n'paste from one of bugreports, sent to me, as FreeBSD ports maintainer. All these bugreports (about perl and python) was raised just after update swig to 1.3.25 in FreeBSD ports system.
Today I'll try to reproduce problem with python and send more information about it.
MB> Workaround:
MB> Change the two occurrences of "SWIGEXPORT(foobar)" to "SWIGEXPORT
MB> foobar" in subversion/bindings/swig/core.i
Thank you!
--
Best regards,
Lev mailto:lev@serebryakov.spb.ru
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: Re[2]: SWIG 1.3.25: subversion can not be build with it :(
Posted by Max Bowsher <ma...@ukf.net>.
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
Re[2]: SWIG 1.3.25: subversion can not be build with it :(
Posted by Lev Serebryakov <le...@serebryakov.spb.ru>.
Hello Ben,
Sunday, July 3, 2005, 11:09:44 PM, you 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?
BCS> I don't understand, the CHANGES entry for svn 1.1.4 says:
BCS> * add SWIG 1.3.24 and .25 compatibility (r12551, r12717-9, r12722,
BCS> r13504)
BCS> So, what's going on here?
I see what I see: with swith-1.3.23 everything is Ok, 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
And for perl:
/usr/local/bin/swig -noproxy -nopm -perl
-I../../../../../subversion/bindings/swig
-I../../../../../subversion/bindings/swig/perl/libsvn_swig_perl
-I../../../../../subversion/include -I/usr/local/include/apache2 -o
core.c ../../../../../subversion/bindings/swig/core.i
../../../../../subversion/bindings/swig/core.i:499: Warning(453): Can't
apply (apr_hash_t *PROPHASH). No typemaps are defined.
../../../../../subversion/bindings/swig/core.i:499: Warning(453): Can't
apply (apr_hash_t *PROPHASH). No typemaps are defined.
../../../../../subversion/bindings/swig/core.i:510: Warning(453): Can't
apply (apr_array_header_t **OUTPUT_OF_PROP). No typemaps are defined.
../../../../../subversion/bindings/swig/core.i:510: Warning(453): Can't
apply (apr_array_header_t **OUTPUT_OF_PROP). No typemaps are defined.
../../../../../subversion/bindings/swig/core.i:510: Warning(453): Can't
apply (apr_array_header_t **OUTPUT_OF_PROP). No typemaps are defined.
/usr/local/libexec/ccache/cc -c -I/usr/local/include/apache2
-I/usr/local/include/apache2 -I/usr/local/include
-I../../../../../subversion/bindings/swig/perl/libsvn_swig_perl
-I../../../../../subversion/include
-I../../../../../subversion/bindings/swig -g
-DAPPLLIB_EXP="/usr/local/lib/perl5/5.8.7/BSDPAN" -DHAS_FPSETMASK
-DHAS_FLOATINGPOINT_H -fno-strict-aliasing -pipe -I/usr/local/include
-Os -pipe -march=pentium4 -DVERSION=\"\" -DXS_VERSION=\"\" -DPIC
-fPIC "-I/usr/local/lib/perl5/5.8.7/mach/CORE" core.c
core.c: In function `SWIG_Perl_ConvertPtr':
core.c:708: warning: cast to pointer from integer of different size
core.c: At top level:
core.c:1139: error: syntax error before "apr_pool_t"
*** Error code 1
It is subversion 1.2.0 in both cases.
--
Best regards,
Lev mailto:lev@serebryakov.spb.ru
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: SWIG 1.3.25: subversion can not be build with it :(
Posted by Ben Collins-Sussman <su...@collab.net>.
On Jul 3, 2005, at 12:29 PM, Lev Serebryakov wrote:
> Hello users,
>
> 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?
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?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org