Ralph/all,
Ralph Castain wrote:
Unfortunately, that's all that is available at the moment. Future
releases (post 1.1) may get around this problem.
The issue is that the bproc launcher actually does a binary memory image
of the process, then replicates that across all the nodes. This is how
we were told to implement it originally by the BProc folks. However,
that means that shared libraries have problems, for obvious reasons.
We have to reimplement the bproc launcher using a different approach -
will take a little time.
The current launcher does work w/ shared libraries, if they are available
on the backend nodes. So, it's more convienent if they are linked statically,
but not a requirement.
Tim
Ralph
David Gunter wrote:
Unfortunately static-only will create binaries that will overwhelm
our machines. This is not a realistic option.
-david
On Apr 11, 2006, at 1:04 PM, Ralph Castain wrote:
Also, remember that you must configure for static operation for
bproc - use the configuration options "--enable-static --disable-
shared". Our current bproc launcher *really* dislikes shared
libraries.... ;-)
_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
------------------------------------------------------------------------
_______________________________________________
users mailing list
us...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/users
