0

This is a head scratcher.

Below is the output of ldconfig -p | grep libncur* :

libncursesw.so.5 (libc6,x86-64) => /usr/lib64/libncursesw.so.5
libncursesw.so (libc6,x86-64) => /usr/lib64/libncursesw.so
libncurses.so.5 (libc6,x86-64) => /usr/lib/libncurses.so.5
libncurses.so.5 (libc6,x86-64) => /usr/lib64/libncurses.so.5
libncurses.so.5 (libc6,x86-64) => /lib/libncurses.so.5
libncurses.so (libc6,x86-64) => /usr/lib64/libncurses.so

This is the error I get:

/cass/bin/m050ub02: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory

Clearly the libraries are listed in the ldconfig cache, but it can't seem to find them.

3
  • 2
    What do file /cass/bin/m050ub02 and ldd /cass/bin/m050ub02 output? Jul 11, 2017 at 15:00
  • is the calling process overriding LD_LIBRARY_PATH?
    – Jeff Schaller
    Jul 11, 2017 at 16:03
  • "cannot open shared object file: No such file or directory" - you could run it under strace to show us the path(s) it is trying to open. Use strace -e open if there is too much output to find it.
    – sourcejedi
    Jul 11, 2017 at 19:06

2 Answers 2

3

Try this:

strace -e open /cass/bin/m050ub02

this should tell you what the binary is trying to open. Also try

echo $LD_LIBRARY_PATH

and see if your libraries are in there. If not, try symlinking them somewhere on that path.

1

The problem has been solved. It turns out they were 64-bit libraries, I found a 32-bit, and everything works perfectly now.

1
  • There's something wrong with your configuration. A program should not be looking for 32-bit libraries in /usr/lib64. Jul 13, 2017 at 23:34

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .