FS#62513 - [subversion] fails to build with SWIG-4.0.0
Attached to Project:
Arch Linux
Opened by Douglas R. Reno (renodr) - Tuesday, 30 April 2019, 20:47 GMT
Last edited by Felix Yan (felixonmars) - Sunday, 13 September 2020, 20:45 GMT
Opened by Douglas R. Reno (renodr) - Tuesday, 30 April 2019, 20:47 GMT
Last edited by Felix Yan (felixonmars) - Sunday, 13 September 2020, 20:45 GMT
|
Details
Description:
Hi folks, When we updated Beyond Linux From Scratch to SWIG-4.0.0, we noticed that there was a problem with subversion's build procedure. It tries to use the '-classic' CLI option in SWIG that was originally for Python-2.2 bindings. I noticed that you guys generate the python bindings to Subversion as well, so I figured I'd share my experience here with you. To fix this, we are implementing a sed to remove the -classic option: sed -i /-classic/d build_outputs.mk This seemed to fix the FTBFS for us. When you update to SWIG-4, this might come in handy. Additional info: * package version(s) Subversion-1.12.0 and SWIG-4.0.0 (SWIG not updated in Arch yet) * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: 1) build Subversion-1.12.0 with SWIG-4.0.0 1a) build will fail due to removed CLI option in SWIG I hope this helps you guys out if you need to do a rebuild of subversion with SWIG. I also hope this is the right place to let you guys know about this, and if it isn't, I apologize for the noise. |
This task depends upon
Closed by Felix Yan (felixonmars)
Sunday, 13 September 2020, 20:45 GMT
Reason for closing: Fixed
Additional comments about closing: 1.14.0-1
Sunday, 13 September 2020, 20:45 GMT
Reason for closing: Fixed
Additional comments about closing: 1.14.0-1
"error: ‘svn_argnum_swig_obj’ undeclared"
[1] https://github.com/archlinux/svntogit-packages/commit/5b7b15d14b20d5985e36c17432f80168926b9fd2