On Tue, 2009-02-24 at 13:30 -0500, Jeff Squyres wrote:
> - Get Python to give you the possibility of opening dependent
> libraries in the global scope. This may be somewhat controversial;
> there are good reasons to open plugins in private scopes. But I have
> to imagine that OMPI is not th
On Feb 24, 2009, at 1:07 PM, Jeff Squyres wrote:
The minimpi(.py) Python module loads the minimpiext(.c) module and
calls
its minimpiext.init() method (defined in minimpiext.c) which in turn
calls MPI_Init(). "minimpiext.c" is linked against libmpi. Libmpi is
loaded as soon as Python evaluates
On Feb 24, 2009, at 11:32 AM, > wrote:
The minimpi(.py) Python module loads the minimpiext(.c) module and
calls
its minimpiext.init() method (defined in minimpiext.c) which in turn
calls MPI_Init(). "minimpiext.c" is linked against libmpi. Libmpi is
loaded as soon as Python evaluates "import
> > 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
