Skip compilation symbol resolution while creating Linux shared libraries with dependencies

Question

Is there a gcc flag to skip character resolution by the linker during linking when creating a shared library (which depends on other shared libraries)? For some reason, my toolchain gives errors undefined referencewhen I try to create a common C library that depends on B.so and A.so, although dependencies are defined and exist. I heard that the gcc flag exists to defer resolving dependencies at runtime.

Answer 1

I think what you are looking for --allow-shlib-undefined. From the ldman page :

--allow-shlib-undefined
--no-allow-shlib-undefined
    Allows (the default) or disallows undefined symbols in shared libraries. 
    This switch is similar to --no-undefined except that it determines the 
    behaviour when the undefined symbols are in a shared library rather than 
    a regular object file. It does not affect how undefined symbols in regular
    object files are handled.

    The reason that --allow-shlib-undefined is the default is that the shared
    library being specified at link time may not be the same as the one that 
    is available at load time, so the symbols might actually be resolvable at 
    load time. Plus there are some systems, (eg BeOS) where undefined symbols 
    in shared libraries is normal. (The kernel patches them at load time to 
    select which function is most appropriate for the current architecture. 
    This is used for example to dynamically select an appropriate memset 
    function). Apparently it is also normal for HPPA shared libraries to have
    undefined symbols.

Allow undefined characters by default, however, so I assume that your problem is actually something else.