[jira] [Created] (SVN-4818) Failed to build with SWIG 4

"Felix Yan (JIRA)" <[email protected]>
Newsgroups gmane.comp.version-control.subversion.issues
Message-ID <[email protected]>
Felix Yan created SVN-4818:
------------------------------

             Summary: 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


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
(v7.6.3#76005)
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.