In this particular case on Gentoo we stole patches from fedora to autotool it. Which is why I have a .so. And someone did a copy/paste from another package when autotooling it and forgot to replace some “readline” by “gmp” - oops.
I am not even sure how you are supposed to tell pristine bliss if you want to use gmp or not. Likely not by default or you would have to provide gmp/mpir at some point when linking sage/graphs/bliss.so. You should look in the log file from the sage build to see if -lgmp was passed during the linking of the above shared object. But yes it is so much better to have a soname or equivalent to rely on. Provided they are used properly. François > On 13/12/2015, at 12:17, Volker Braun <[email protected]> wrote: > > On Saturday, December 12, 2015 at 10:24:34 PM UTC+1, Dima Pasechnik wrote: > indeed, it's static library for me: > $ ls -l local/lib/*blis* > -rw-rw-r-- 1 dima dima 3123674 Nov 10 12:28 local/lib/libbliss.a > > Thats correct, and nicely illustrates what a massive liability static > libraries are for Sage. Suddenly its near impossible to tell which > dependencies libbliss uses. And the real fun starts once you upgrade > libbliss, you'll never know whether a binary is using the right version of > libbliss. > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/sage-devel. > For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
