Re: [OMPI users] problem with MPI_Comm_spawn in 1.6.5 but not 1.4.3 or 1.8.4

Appreciate it - but as I said in my prior note, we aren’t maintaining 1.6 any more, so an upgrade to 1.8 (which worked, as you noted) is in order > On Mar 13, 2015, at 8:23 AM, Chris Paciorek > wrote: > > And the promised attachment. > > On Thu, Mar 12, 2015 at 6:11 PM, Chris Paciorek > mail

Re: [OMPI users] problem with MPI_Comm_spawn in 1.6.5 but not 1.4.3 or 1.8.4

And the promised attachment. On Thu, Mar 12, 2015 at 6:11 PM, Chris Paciorek wrote: > I'm having an issue with MPI_Comm_spawn not starting workers on the > nodes provided via -machinefile or -host. This is occurring on Ubuntu > 14.04/14.10 with openMPI 1.6.5. However, I do not have the problem on

Re: [OMPI users] Process Binding Warning

Thank you. It worked! On Fri, Mar 13, 2015 at 10:37 AM, Ralph Castain wrote: > You shouldn’t have to do so > > On Mar 13, 2015, at 7:14 AM, Saliya Ekanayake wrote: > > Thanks Ralph. Do I need to specify where to find numactl-devel when > compiling OpenMPI? > > On Thu, Mar 12, 2015 at 7:17 PM, R

Re: [OMPI users] Process Binding Warning

You shouldn’t have to do so > On Mar 13, 2015, at 7:14 AM, Saliya Ekanayake wrote: > > Thanks Ralph. Do I need to specify where to find numactl-devel when compiling > OpenMPI? > > On Thu, Mar 12, 2015 at 7:17 PM, Ralph Castain > wrote: > You are missing the numactl a

Re: [OMPI users] Process Binding Warning

Thanks Ralph. Do I need to specify where to find numactl-devel when compiling OpenMPI? On Thu, Mar 12, 2015 at 7:17 PM, Ralph Castain wrote: > You are missing the numactl and numactl-devel packages on that compute > node, and so we cannot bind the memory to the same location as your proc. > As t