Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. 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#39533 - [sage-mathematics] broken after bash 4.3 update

Attached to Project: Community Packages
Opened by Antonio Rojas (arojas) - Tuesday, 18 March 2014, 21:38 GMT
Last edited by Evgeniy Alexeev (arcan1s) - Thursday, 20 March 2014, 08:19 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Evgeniy Alexeev (arcan1s)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
The bash 4.3 update breaks Sage. At startup or when using help one gets the error:

sh: symbol lookup error: sh: undefined symbol: rl_signal_event_hook

and the notebook doesn't start. Rebuilding fails with the same error, and building with system readline fails too when building the python readline module.

I fixed it locally by removing /opt/sage/local/lib/libreadline.* and replacing it with symlinks to /usr/lib/libreadline.*
This task depends upon

Closed by  Evgeniy Alexeev (arcan1s)
Thursday, 20 March 2014, 08:19 GMT
Reason for closing:  Fixed
Additional comments about closing:  6.1.1-2
Comment by Evgeniy Alexeev (arcan1s) - Wednesday, 19 March 2014, 06:48 GMT
As far as I know, the current version of python2 doesn't work correctly with the current version of readline (there is a bug report: http://bugs.python.org/issue20374 ). Also I don't sure that symlinking of readline is a correct way. I'll try to build sage with system readline, but if it doesn't help I'll use your way.
Comment by Evgeniy Alexeev (arcan1s) - Wednesday, 19 March 2014, 23:38 GMT
Ok, I've built sage using system readline with python patch. I've tested it localy and it looks like it works normally. I push it in our repo
Comment by Antonio Rojas (arojas) - Thursday, 20 March 2014, 08:01 GMT
I confirm it's working fine here. Thanks for the quick fix!

Loading...