Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/index.php/Reporting_Bug_Guidelines

Do NOT report bugs when a package is just outdated, or it is in Unsupported. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

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 Levente Polyak (anthraxx) - Wednesday, 31 July 2019, 22:45 GMT
Task Type Bug Report
Category Packages: Extra
Status Assigned
Assigned To Felix Yan (felixonmars)
Architecture All
Severity High
Priority Urgent
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 1
Private No

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

Comment by Antonio Rojas (arojas) - Monday, 27 May 2019, 17:20 GMT
Your sed actually removes the entire line, so no python bindings are compiled at all. If you really just remove the -classic flag, there are many further failures with
"error: ‘svn_argnum_swig_obj’ undeclared"
Comment by Levente Polyak (anthraxx) - Wednesday, 31 July 2019, 22:44 GMT
I'm raising this to high/urgent as its holding back an unauthenticated remote DoS fix

Loading...