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 li
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 depe
On Sat, Feb 13, 2016 at 2:27 PM, Nick Papior wrote:
>
>
> 2016-02-13 23:07 GMT+01:00 Kim Walisch :
>
>> Hi,
>>
>> > You may be interested in reading:
>> https://www.open-mpi.org/software/ompi/versions/
>>
>> Thanks for your answer. I found:
>>
>> > Specifically: v1.10.x is not guaranteed to be ba
2016-02-13 23:07 GMT+01:00 Kim Walisch :
> Hi,
>
> > You may be interested in reading:
> https://www.open-mpi.org/software/ompi/versions/
>
> Thanks for your answer. I found:
>
> > Specifically: v1.10.x is not guaranteed to be backwards
> compatible with other v1.x releases.
>
> And:
>
> > However
Hi,
> You may be interested in reading:
https://www.open-mpi.org/software/ompi/versions/
Thanks for your answer. I found:
> Specifically: v1.10.x is not guaranteed to be backwards
compatible with other v1.x releases.
And:
> However, this definition only applies when the same version of Open
MP
You may be interested in reading:
https://www.open-mpi.org/software/ompi/versions/
2016-02-13 22:30 GMT+01:00 Kim Walisch :
> Hi,
>
> In order to make life of my users easier I have built a fully
> statically linked version of my primecount program. So the program
> also statically links against
