Re: dlopen and shared library dependencies

["James K. Lowden" <jklowden%schemamania.org@localhost>]

Brook Milligan wrote:
> Consider shared library A that depends on (i.e., has undefined symbols
> that are resolved by) library B, and that this is all noted within A
> with the correct rpath, etc.  If library A is loaded with dlopen, will
> library B also be loaded to resolve the symbols or will the symbols
> just be unresolved?  

The manual also says:

        "The shared object is mapped into the address space, relocated and its
external references are resolved in the same way as is done with the
implicitly loaded shared libraries at program startup."

It's common for a shared library to have its own unresolved symbols, not
least because it relies on, say, libc.  

HTH.

--jkl