libtinfo.so.5: no version information available

3,167 views
Skip to first unread message

Harald Schilly

unread,
Jul 17, 2016, 6:27:27 AM7/17/16
to sage-devel
Hi, when I'm compiling sage (either from develop or 7.2), I'm getting lots and lots of error lines like:

/bin/sh: /ext/sage/7.2/local/lib/libtinfo.so.5: no version information available (required by /bin/sh)

It's in a docker container, running normal recent ubuntu, and I have no real clue what I should try in order to get rid of this. Maybe it's just some env variable? I'm aware that this error did already came up here, and Volker's idea was to delete this file and rebuild. Besides that, does anyone have some experience with this error?

-- harald

Volker Braun

unread,
Jul 17, 2016, 8:49:12 AM7/17/16
to sage-devel
do you have LD_LIBRARY_PATH or LD_PRELOAD set?

Harald Schilly

unread,
Jul 17, 2016, 1:14:02 PM7/17/16
to sage-devel


On Sunday, July 17, 2016 at 2:49:12 PM UTC+2, Volker Braun wrote:
do you have LD_LIBRARY_PATH or LD_PRELOAD set?

No, nothing like that is set. I also tried to clean up and start building again, but it did appear again. It's also a bit strange, because this error seems to come and go erratically. I'll try to see if I can notice something more concrete.

-- h

leif

unread,
Jul 17, 2016, 2:03:49 PM7/17/16
to sage-...@googlegroups.com
R U building as root?!?!??

Never do that, or fix the ncurses package... ;-)


-leif


Dominique Laurain

unread,
Jul 17, 2016, 2:34:49 PM7/17/16
to sage-devel
In order to get version information (required by shell):
objdump -x libntl.so 

check symbolic links, for example in my local install (Ubuntu 14.04, sage-6.9) I have in the sage-src/sage-6.9/local/lib directory two links:
libntl.so and libntl.so.16 pointed to the dynamic library file libntl.so.16.0.0

restart your operating system to unload the dynamic libraries (Note: I don't know how to restart a "docker container")

Dominique

leif

unread,
Jul 21, 2016, 4:30:10 AM7/21/16
to sage-...@googlegroups.com
Could you track this down?

I'm really curious.


-leif


Harald Schilly

unread,
Jul 21, 2016, 5:12:16 AM7/21/16
to sage-...@googlegroups.com
On Thu, Jul 21, 2016 at 10:25 AM, leif <not.r...@online.de> wrote:
> Could you track this down?
>
> I'm really curious.

well, so far no chance. there is definitely nothing LD* related set by
me, but my hunch is, that it might be a side effect of building R as
part of sagemath -- but it could be another package and I just saw it
while building R. My plan is to fix some other details with that build
and then rerun it completely from scratch. If it happens again, maybe
I should upload the build log …

-- h

leif

unread,
Jul 21, 2016, 5:51:17 AM7/21/16
to sage-...@googlegroups.com
Ah, R...

It wouldn't surprise me since R at least used to do horrible things, but
then the error messages should only occur in the R build log.

(I initially thought your ld.so.cache got messed up, and you were
getting the error even outside of Sage. Nice idea by Ubuntu to
dynamically link even /bin/sh to more than libc by the way.)


-leif


Reply all
Reply to author
Forward
0 new messages