On Wednesday, August 30, 2017 at 6:14:06 PM UTC+1, Richard_L wrote: > > As I observed on the sage-release Sage.8.1.beta3 thread, a library > conflict causes 'make ptestlong' to fail under openSUSE LEAP 42.2. > Reworking the offending symlink in the sage installation to point to the > system library fixes the problem. The two copies of "libreadline.so.6.3" > are NOT identical. Running 'nm -D --defined-only' against each file, and > stripping out the symbol values, I was able to diff the two, revealing > discrepancies both in symbol types and symbol names. (Log attached.) > > Question: Why does sage install shared-object libraries when working > versions of same are already on the system? >
it is one of the curses/blessings of a distribution-like system like Sage; it is easier and more reliable, generally speaking, to rely on a particular version of a library/package than to work around bugs/(mis)features of a system-wide installed library/package. Normally speaking, such a library clash that you see should not happen. Do you have something special in your setup that causes this mis-linking? (say, set LD_LIBRARY_PATH...) > - Richard > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
