LD_LIBRARY_PATH doesn't work for current directory (library has correct architecture)

Asked Sep 24 '17 at 02:22

Active Sep 24 '17 at 16:51

Viewed 1,066 times

I have an executable and its dependency libraries in the same path, but the former isn't finding the latter:

$ LD_LBRARY_PATH='.' ./img_matcher
./img_matcher: error while loading shared libraries: libmlx_common_atoms.so: cannot open shared object file: No such file or directory

$ file img_matcher
img_matcher: ELF 64-bit LSB  executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=7cd572700424d204833657090a7e25b98ec3b819, not stripped

$ file libmlx_common_atoms.so 
libmlx_common_atoms.so: ELF 64-bit LSB  shared object, x86-64, version 1 (GNU/Linux), dynamically linked, BuildID[sha1]=167baeeefe4b2692b455d38571dc85328ce8ed7f, not stripped

What am I missing?

edited Sep 24 '17 at 16:51

asked Sep 24 '17 at 02:22

Dustin Oprea

9,673
13
65
105

The fact that one is `SYSV`, and the other is `GNU/Linux` may have something to do with it. – Employed Russian Sep 24 '17 at 23:18
Possibly related: https://stackoverflow.com/q/45783759/50617 – Employed Russian Sep 24 '17 at 23:19
Hmm. I missed that. Thanks for pointing it out. – Dustin Oprea Sep 25 '17 at 02:23

LD_LIBRARY_PATH doesn't work for current directory (library has correct architecture)

0 Answers0