You might try to move one of them out of the way and replace it by (a link to ?) the other, to see what happens
- when you use Sage - when you use some software on your system using libreadline The result(s) may help to determine the "right" tqrget for debugging the problem. HTH, -- Emmanuel Charpentier Le mercredi 30 août 2017 00:27:14 UTC+2, [email protected] a écrit : > > Thanks, Emmanuel. > > Indeed, ldconfig -p gives the following: "libreadline.so.6 (libc6,x86-64) > => /lib64/libreadline.so.6". The latter is a symbolic link to > /lib64/libreadline.so.6.3, owned by root. > In the folder ~/Development/sage/local/lib/, ./libreadline.so.6 is a > symbolic link to ./libreadline.so.6.3 (owned by rllozes), as expected. > > So, I have two symlinks, both presumably visible(?) and both pointing to > valid, versioned libraries. How would that confuse the make? I don't find > any other similarly named files. > > - Richard > > On Tuesday, August 29, 2017 at 6:11:30 AM UTC-7, Emmanuel Charpentier > wrote: >> >> In the three cases, the culprit is the unexpected message : >> >> sh: /home/rllozes/Development/sage/local/lib/libreadline.so.6: no version >> information available (required by sh) >> >> >> Do you have an unexpected libreadline in your library path ? >> >> ... >> > -- You received this message because you are subscribed to the Google Groups "sage-release" 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-release. For more options, visit https://groups.google.com/d/optout.
