Hi, On 2024-10-18 07:57, Jun Omae wrote:
On 2024/10/14 16:37, Yasuhito FUTATSUKI wrote:On 2024/10/14 12:37, Yasuhito FUTATSUKI wrote:It seems it is caused by backward incompatible change of SWIG, even it may be a bug.It turned out this is not a bug of SWIG, but intentional, for the purpose to fix another problem, incompatible change of SWIG_Ruby_AppendOutput, SWIG_Python_AppendOutput (and it affect the process how we construct result objects).Thanks,SWIG 4.3.0-beta1 doesn't work with swig-rb and swig-py bindings, for our use case that the svn_error_t * return value is not used as a return value on success and is raised as an exception on error. Also, our %typemap(out) which uses %append_output for swig-rb has issues. I created patches and tested with SWIG 3.0.12, 4.2.1, 4.3.0-beta1. - swig-4.3.0-swig-rb.patch.txt (swig-rb for trunk and 1.14.x) - swig-4.3.0-swig...@trunk.patch.txt (swig-py for trunk) - swig-4.3.0-swig...@1.14.x.patch.txt (swig-py for 1.14.x) Could anybody please test the patches?
Builds and tests (testsuite) fine for me on:
* trunk x {4.2.1,4.3.0-beta1} * 1.14.3 x {4.2.1,4.3.0-beta1}
Andreas
