I didn't change nothing in /etc/ld.so.conf.d". I mean I checked what directories with libraries are written there and then I made symlinks accordingly.DougieLawson wrote:After you update /etc/ld.so.conf.d you MUST run depmod -a to ensure all the library info is built into the system files. It's not good enough to just reboot, you may need to do that after running depmod.
I think you've confused depmod (which rebuilds the kernel module dependency tables) and ldconfig (which rebuilds the system library tables).DougieLawson wrote:If you add any new library or symlink to a library run depmod.
I was puting "ldconfig" usually always after some changes in library paths.rpdom wrote:I think you've confused depmod (which rebuilds the kernel module dependency tables) and ldconfig (which rebuilds the system library tables).DougieLawson wrote:If you add any new library or symlink to a library run depmod.
There's no kernel modules involved here, so sudo ldconfig should be run.
I wrote in the first post I did it.DougieLawson wrote:Have you followed the instructions here: http://www.ftdichip.com/Drivers/D2XX/Li ... -linux.txt
But I don't think it's a problem with device. It's a problem with OS.DougieLawson wrote:Then you'll need to ask FTDI for support.
It's their library code that you're trying to install.seprob wrote:But I don't think it's a problem with device. It's a problem with OS.DougieLawson wrote:Then you'll need to ask FTDI for support.
But when I want to execute the program it doesn't see the shared object.DougieLawson wrote:It's their library code that you're trying to install.seprob wrote:But I don't think it's a problem with device. It's a problem with OS.DougieLawson wrote:Then you'll need to ask FTDI for support.
I am so surprised but it helped. They send me back correct files (libftd2xx.so.1.1.12 and libftd2xx.a) and I replaced them and then everything went good.DougieLawson wrote:Go and ask the people who wrote the code. Because there's no other way to get this thing to work.