[
https://issues.apache.org/jira/browse/SVN-4818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17767312#comment-17767312
]
Yasuhito Futatsuki commented on SVN-4818:
-----------------------------------------
Because of the reason I described above, we decided that we don't support
building Python 2 bindings with SWIG 4 (won't fix).
For Python 3, the issue was fixed in r1869853 (between 1.13.0 and 1.14.0) for
Unix/Linux and in r177338 (on trunk), r188482 (on 1.14.x branch between 1.14.0
and 1.14.1) for Windows.
> Next error is inside Ruby bindings:
{{> subversion/bindings/swig/ruby/svn_client.c:1605:21: error:
>‘SWIG_POINTER_NO_NULL’ undeclared (first use in this function); did you mean
‘SWIG_POINTER_OWN’?}}
> Looks like the vendored proxy/*.swg files are outdated. I removed some and
> get passed this one.
It was needed to do "make clean-swig" after autogen.sh and configure, before
building swig bindings.
We added an optional step "Clean Old Bindings Intermediate Source Files" as
below, in the install instruction described in subversion/bindings/swig/INSTALL
file.
"Step 2.5 [Optional] Clean Old Bindings Intermediate Source Files
If you are rebuilding bindings with different version of SWIG from
previously used, run 'make clean-swig'. This will clean SWIG version
depended intermediate source files. This step also needs if you are
using the Subversion distribution tarball and using autogen.sh to
rebuild configure script, because you might use different version of
SWIG from one we used to make the tarball."
> Failed to build with SWIG 4
> ---------------------------
>
> Key: SVN-4818
> URL: https://issues.apache.org/jira/browse/SVN-4818
> Project: Subversion
> Issue Type: Bug
> Components: bindings_swig
> Affects Versions: 1.12.0
> Environment: Arch Linux x86_64, SWIG 4.0.0.
> Reporter: Felix Yan
> Priority: Major
> Fix For: trunk, 1.14.1
>
>
> The Python binding failed to build with an error:
> {{Deprecated command line option: -classic. This option is no longer
> supported.}}
> After fixing this (by removing -classic from build.conf), a lot of new
> errors like below appeared:
> {{subversion/bindings/swig/python/svn_client.c:6201:128: error:
> ‘svn_argnum_swig_obj’ undeclared (first use in this function); did you mean
> ‘svn_argnum_obj1’?}}
> After looking up the changelog of SWIG 4, it appears fastunpack becomes
> default so I added {{-nofastunpack}} to get around this.
> Next error is inside Ruby bindings:
> {{subversion/bindings/swig/ruby/svn_client.c:1605:21: error:
> ‘SWIG_POINTER_NO_NULL’ undeclared (first use in this function); did you mean
> ‘SWIG_POINTER_OWN’?}}
> Looks like the vendored proxy/*.swg files are outdated. I removed some and
> get passed this one.
> Finally it built fine, but I am stuck at the test suite now. The python
> binding failed to import correctly:
> {{File
> "/home/felix/projects/arch/packages/subversion/trunk/src/subversion-1.12.0/subversion/bindings/swig/python/libsvn/core.py",
> line 32, in _swig_setattr_nondynamic}}
> {{method = class_type.__swig_setmethods__.get(name, None)}}
> {{AttributeError: type object 'svn_auth_cred_simple_t' has no attribute
> '__swig_setmethods__'}}
> Please let me know how to proceed, thanks!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
