> Don't search, I found the problem.
> It was a library needed by the library I wanted to load that was missing.
> I've a second question:
> Is there a way to find the name of the missing module in such a case?
Usually there exists a program called "ldd" (at least under Solaris,
and (Open|Free|Net)BSD) which lists all libraries an executable or a
depends on; if such a dependency cannot be satisfied, you'll see it in
output of ldd:
libc.so.1 => /usr/lib/libc.so.1
libdl.so.1 => /usr/lib/libdl.so.1
libpthread.so.1 => /usr/lib/libpthread.so.1
libthread.so.1 => /usr/lib/libthread.so.1
libsocket.so.1 => /usr/lib/libsocket.so.1
libnsl.so.1 => /usr/lib/libnsl.so.1
libposix4.so.1 => /usr/lib/libposix4.so.1
libmp.so.2 => /usr/lib/libmp.so.2
libaio.so.1 => /usr/lib/libaio.so.1
libastkssy1.so => (file not found)
In this example, the library libastkssy1.so cannot be found.