Yes, that is correct: the Open MPI libraries used by all components (to include mpirun and all the individual MPI processes) must be compatible. We usually advise users to use the same version across the board, and that will make things work.
More specifically: it's not enough to statically link your MPI application; you would also need to statically link mpirun and the orteds, too (and/or distribute binaries for the entire Open MPI install, even if they're dynamically linked). On February 15, 2016 at 11:51:39 AM, Dave Love (d.l...@liverpool.ac.uk) wrote: > Jeff Hammond writes: > > > You can rely upon e.g. https://www.mpich.org/abi/ when redistributing MPI > > binaries built with MPICH, but a better option would be to wrap all of your > > MPI code in an implementation-agnostic wrapper and then ship a binary that > > can dlopen a different version wrapper depending on which MPI > > implementation the user has. That would allow you to ship a single binary > > that could use both MPICH and OpenMPI. > > I don't know how it works with MPICH, but in OMPI don't you need all of > the submitting orterun, the linked libraries, and the target ORTE to be > compatible, which a wrapper would need to know? [How is the Fortran ABI > fixed anyhow?] > > I don't think there's a check on that currently, which would be useful > if the info can be propagated. There have been issues on the list due > to host and target ORTE being different, and I've seen them locally. > Producing a clear error with incompatible components (to the extent it's > possible) could save confusion. > _______________________________________________ > users mailing list > us...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users > Link to this post: > http://www.open-mpi.org/community/lists/users/2016/02/28532.php > -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
