"Simon White" <[EMAIL PROTECTED]> writes: > However if one of those modules internally calls a function that is also > marked as being exported it does not necessarily call the function in > its own library. Depending on order it may call the function that > exists in the other library instead. Note that both modules are only > manually loaded and neither are loading symbols from each other.
It may (or may not) help as a workaround to build your modules with -Wl,-Bsymbolic, which tells the linker to bind all symbols locally within the shared object if possible at link time. This will (hopefully) cause the module to be built without an external reference to that symbol, so then there's nothing to go wrong at runtime. Note that this will change other linker behavior. Read the GNU ld documentation for more details on exactly what the option does. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> _______________________________________________ http://lists.gnu.org/mailman/listinfo/libtool
