Certainly. Just make sure you have the headers for both on the node where you
build OMPI so we build the required components. Then we will auto-detect which
one we are running under, so nothing further is required
> On May 10, 2017, at 11:41 AM, Belgin, Mehmet
> wrote:
>
> Hello everyone,
>
On May 10, 2017, at 4:50 PM, Joseph Schuchart wrote:
>
> > - Fix memory allocated by MPI_WIN_ALLOCATE_SHARED to
> > be 64 byte aligned.
>
> The alignment has been fixed to 64 *bit* or 8 byte, just in case someone is
> relying on it or stumbling across that. Verified using 2.1.1 just now.
Oop
Dear OpenMPI developers,
Thanks for the great work and the many fixes in this release. Without
meaning to nitpick here, but:
>
> - Fix memory allocated by MPI_WIN_ALLOCATE_SHARED to
>
> be 64 byte aligned.
The alignment has been fixed to 64 *bit* or 8 byte, just in case someone
is relying
Hello everyone,
Is it possible to compile OpenMPI to support torque and slurm at the same time?
We may end up using torque and slurm on different clusters in the near future
and hoping to continue maintain only one OpenMPI stack in our combined
repository.
Thank you!
-Mehmet
=
Hi,
I tried to install openmpi-master-201705100259-d7ebcca on my "SUSE Linux
Enterprise Server 12.2 (x86_64)" with Sun C 5.14 and gcc-7.1.0 and I still
get the error that I reported for openmpi-master-201704200300-ded63c.
loki openmpi-master-201705100259-d7ebcca-Linux.x86_64.64_gcc 126 grep top
