with 'ldd ' you can find such problems. Then you've to find the path where these libraries are. Then you have to create/expand the environment variable 'SHLIB_PATH'. Either you'll set these pathes during login or at the beginning of a script that starts your executable.
Volmark, thanks in advance, but it is not working, I keep receiving the same message, in fact I used LD_LIBRARY_PATH because our OS is 64 bits to look like this:
>in fact I used LD_LIBRARY_PATH because our OS is 64 bits to look like this: LD_LIBRARY_PATH=/usr/local/lib:/lib:/usr/lib
This is incorrect. It doesn't matter the OS, it matters the architecture and the bitness of the application. In this case you must use SHLIB_PATH for those paths.
Also remove /lib, there is nothing there, it's an illusion.
yes, if you can't find this library with a find-command (from '/') then you have to ask the vendor of the software. Have you tried with wildcards, maybe the lib has a misspelling.
Guys, I found that the software uses a special library, which for some reason it is not being installed at installation time, so I will have to turn this case to HDS, thanks again.
