When an executable needs a shared library or even if a shared library
needs another shared library (I think) and one them doesn’t exists we
have an explicit message saying which library is missing.
Unfortunately, when we load a dll with dlopen() and a ‘sub-library’ is
missing, we only now that one of the needed library is missing but we
don’t know which one. Would it be possible to improve this feaure?
Ok, we can do an objdump, but I guess that dlopen() could do much
better.
When an executable needs a shared library or even if a shared library
needs another shared library (I think) and one them doesn’t exists we
have an explicit message saying which library is missing.
Unfortunately, when we load a dll with dlopen() and a ‘sub-library’ is
missing, we only now that one of the needed library is missing but we
don’t know which one. Would it be possible to improve this feaure?
Ok, we can do an objdump, but I guess that dlopen() could do much
better.
Would you really like it if your library printed messages
to (what could possibly be) a random file descriptor?
Having said that, if you run with the environment variable
DL_DEBUG=1 then you will see load messages on your stderr.
Alain Bonnefoy <> alain.bonnefoy@icbt.com> > wrote:
When an executable needs a shared library or even if a shared library
needs another shared library (I think) and one them doesn’t exists we
have an explicit message saying which library is missing.
Unfortunately, when we load a dll with dlopen() and a ‘sub-library’ is
missing, we only now that one of the needed library is missing but we
don’t know which one. Would it be possible to improve this feaure?
Ok, we can do an objdump, but I guess that dlopen() could do much
better.
Would you really like it if your library printed messages
to (what could possibly be) a random file descriptor?
Having said that, if you run with the environment variable
DL_DEBUG=1 then you will see load messages on your stderr.