Re: [OMPI users] compiling OpenMPI 1.8.4 on system with multiarched SLURM libs (Ubuntu 15.04 prerelease)

2015-02-26 Thread Lev Givon
Received from Ralph Castain on Thu, Feb 26, 2015 at 04:14:05PM EST: > > On Feb 26, 2015, at 1:07 PM, Lev Givon wrote: > > > > I recently tried to build OpenMPI 1.8.4 on a daily release of what will > > eventually become Ubuntu 15.04 (64-bit) with the --with-slurm and --with-pmi > > options on. I

Re: [OMPI users] compiling OpenMPI 1.8.4 on system with multiarched SLURM libs (Ubuntu 15.04 prerelease)

2015-02-26 Thread Ralph Castain
Looks like we don’t have a separate pmi-libdir configure option, so it may not work. I can add one to the master and set to pull it across to 1.8.5. > On Feb 26, 2015, at 1:07 PM, Lev Givon wrote: > > I recently tried to build OpenMPI 1.8.4 on a daily release of what will > eventually become

[OMPI users] compiling OpenMPI 1.8.4 on system with multiarched SLURM libs (Ubuntu 15.04 prerelease)

2015-02-26 Thread Lev Givon
I recently tried to build OpenMPI 1.8.4 on a daily release of what will eventually become Ubuntu 15.04 (64-bit) with the --with-slurm and --with-pmi options on. I noticed that the libpmi.so.0.0.0 library in Ubuntu 15.04 is now in the multiarch location /usr/lib/x86_64-linux-gnu rather than /usr/li

Re: [OMPI users] using MPI_Comm_spawn in OpenMPI 1.8.4 with SLURM

2015-02-26 Thread Ralph Castain
Pretty sure Slurm doesn’t support dynamic spawn - we don’t support it when direct launched using srun. It is only supported when launched by mpiexec Might change in future releases, assuming Slurm has or adds the support > On Feb 26, 2015, at 5:26 AM, Lev Givon wrote: > > I've been using Open

[OMPI users] using MPI_Comm_spawn in OpenMPI 1.8.4 with SLURM

2015-02-26 Thread Lev Givon
I've been using OpenMPI 1.8.4 manually built on Ubuntu 14.04.2 against the PMI libraries provided by the stock SLURM 2.6.5 Ubuntu packages. Although I am able to successfully run MPI jobs that use MPI_Comm_spawn via mpi4py 1.3.1 (also manually built against OpenMPI 1.8.4) to dynamically create proc