FS#65373 - [swig] ruby 2.7 bindings bug.
Attached to Project:
Arch Linux
Opened by bartus (bartus) - Tuesday, 04 February 2020, 14:56 GMT
Last edited by Toolybird (Toolybird) - Thursday, 23 March 2023, 21:12 GMT
Opened by bartus (bartus) - Tuesday, 04 February 2020, 14:56 GMT
Last edited by Toolybird (Toolybird) - Thursday, 23 March 2023, 21:12 GMT
|
Details
There's no way to build `ruby=2.7` bindings with current
version of swig :/
Upstream issue: https://github.com/swig/swig/issues/1689 There's some patches suggestion but no definitive solution yet. Effected packages I'm aware of: AUR/yafaray. |
This task depends upon
Closed by Toolybird (Toolybird)
Thursday, 23 March 2023, 21:12 GMT
Reason for closing: Fixed
Additional comments about closing: swig 4.1.0-1
Thursday, 23 March 2023, 21:12 GMT
Reason for closing: Fixed
Additional comments about closing: swig 4.1.0-1
Could we bring it to Arch without waiting for upstream release, since we ship `ruby=2.7`?
https://github.com/swig/swig/pull/1692
anything preventing to update to swig 4.1.1 and close this ?
I'm also waiting for all the fixes in 4.1
ming [1] does not support python 3 so not really an upstream issue until that is addressed.
libteam [2]
libsigrok [3]
python-pymupdf fails check with swig.4.1.1
[1] https://github.com/libming/libming/issues/177
[2] https://github.com/jpirko/libteam/issues/73
[3] https://sigrok.org/bugzilla/show_bug.cgi?id=1827