Answer the question
In order to leave comments, you need to log in
Why can't the Linux linker see the dynamic library?
There is a Raspberry Pi with the latest Raspbian Wheezy on board and a device with an interface based on an FTDI chip. Libraries were installed for the device (according to the attached manual ). The problem is that programs do not see these libraries.
Let's run the example that comes with the driver:
$ sudo ~/release/examples/EEPROM/read/./read
/home/pi/release/examples/EEPROM/read/./read: error while loading shared libraries: libftd2xx.so: cannot open shared object file: No such file or directory
$ sudo ldd ~/release/examples/EEPROM/read/./read
/usr/lib/arm-linux-gnueabihf/libcofi_rpi.so (0xb6fb5000)
libftd2xx.so => not found
libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6e7a000)
/lib/ld-linux-armhf.so.3 (0xb6fc3000)
$ sudo ldconfig -v
/usr/local/lib:
libftd2xx.so -> libftd2xx.so.1.1.12
/usr/lib:
libftd2xx.so -> libftd2xx.so.1.1.12
Answer the question
In order to leave comments, you need to log in
The question is removed.
I pulled out the same library (libftd2xx.so) from a year-old backup, put it where it was needed and it all worked. I checked the files - the libraries have the same version (judging by the name), but the size is different.
The conclusion is that these Asians messed up something with the files on their site, so the library downloaded a year ago on Arch works, but the one downloaded now on fresh Debian no longer works.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question