Hello,
I have a runtime-linking problem with MPI 1.3 that is very similar.
We apply MPI in a Python-based framework. For some platforms we use a
patched Python version that does the MPI_Init() call.
On some machines we use an unmodified Python with a small module
(minimpi) that cares for the MPI_
> > Upon further investigation, it seems to be a problem similar to
this:
> > http://www.open-mpi.org/community/lists/devel/2005/09/0359.php
> > The dynamic parts of the library are however no more linked against
> > their frameworks.
> I looked at your tarball -- I don't know anything about Pytho
Thanks for the hints.
> You have some possible workarounds:
>
> - We recommended to the PyMPI author a while ago that he add his own
> dlopen() of libmpi before calling MPI_INIT, but specifically using
> RTLD_GLOBAL, so that the library is opened in the global process space
> (not a private
>> That would involve patching Python in some nifty places which would
>> probably lead to less Platform independence, so no option yet.
> I should have been more clear: what I meant was to engage the Python
> community to get such a feature to be implemented upstream in Python
> itself. Since
