I used to have the exact same problem (with libtinfo*) back when Sage 
shipped ncurses 5 (to which libtinfo* belong). My workaround was to move 
libtinfo* out of the way : Sage the used the systemwide libtinfo*.

A recent upgrade to the Sage-shipped ncurses (which is now version 6) fixed 
this.

IMHO, these libraries would be a nice target to an attempt (in the 
configure file) for testing a possible systemwide library, then do NOT 
install the Sage-shipped version if the systemwide version is sufficient. I 
have been told that this already happens for some Sage-shipped packages, 
but I'm unable to quote them

 I'd like to propose a patch (at least for libreadline and ncurses), but I 
miss a couple of informations :

   - How to tell "configure" not to install the Sage-shipped version ? I 
   think I am able to look at the configuration of the Sage-shipped packages 
   for which this happens in order  to understand what is done and clone/adapt 
   the process. What are they ?
   - What features are necessary in {libtinfo|libreadline|wwhatever} for 
   Sage to run correcly (i. e. what should "configure" test) ?


Ideas ?

--
Emmanuel Charpentier

Le mercredi 30 août 2017 19:14:06 UTC+2, Richard_L a écrit :
>
> 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?
>
>  - 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.

Reply via email to