No. LD_LIBRARY_PATH is not set. The curious thing is that there are 29 lib*.so in the sage/local/lib folder that are in common with the system /lib64 folder, although not necessarily of the same version/sub-version. Only libreadline.so gives trouble during make ptestall.
NB! Just grep'd all of ~/Development/sage/ for the string "no version information". I find 6427 similar messages involving libreadline in the pkg logs. The messages are distributed across logs/pkgs/arb-2.8.1.p1.log: 1566 logs/pkgs/flint-2.5.2.p1.log: 4614 logs/pkgs/r-3.4.0.p0.log: 241 logs/pkgs/rpy2-2.8.2.p0.log: 6 So, although the installation script complains mightily, it chugs along and gives an apparently healthy installation! Tnx, - Richard On Thursday, August 31, 2017 at 1:07:50 AM UTC-7, Dima Pasechnik wrote: > > > 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...) > > > -- 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.
