Re: linking with 2 different mpi libraries

From: Toon Knapen (toon.knapen_at_[hidden])
Date: 2004-06-29 06:31:14

(sorry for not replying earlier but I never received Vladimirs response 
but saw it accendently listed in the archive)

Vladimir Prus wrote:

> Toon Knapen wrote:
>> A second problem comes up when my framework is compiled to shared 
>> libraries instead of static libraries. When linking the shared library, 
>> all dependencies need to be provided on the link-line. However these 
>> dependencies are different if the framework-library will be used in a 
>> sequential or a parallel application.
> I'm not sure I follow. On Unix, shared libraries can have
> unresolved references, which will be finally resolved during
> linking of exe. I think it's not that case on Windows, though.
But even when linking with all dependencies the symbol remains undefined 
in my shared library. However an 'ldd <my-so>' shows that my-so nows 
where it can find the other libaries to resolve the undefined symbols.

If I don't link my-so with its dependencies, importing it in Python will 
result in an error about undefined symbols.