On 20 April 2017 at 12:58, r...@open-mpi.org <r...@open-mpi.org> wrote: > Fully expected - if ORTE can’t start one or more daemons, then the MPI job > itself will never be executed. > > There was an SGE integration issue in the 2.0 series - I fixed it, but IIRC > it didn’t quite make the 2.0.2 release. In fact, I just checked and it did > indeed miss that release. > > You have three choices: > > 1. you could apply the patch to the 2.0.2 source code yourself - it is at > https://github.com/open-mpi/ompi/pull/3162 > > 2. download a copy of the latest nightly 2.0.3 tarball - hasn’t been > officially released yet, but includes the patch > > 3. upgrade to the nightly 2.1.1 tarball - expected to be officially released > soon and also includes the patch > > Hopefully, one of those options will fix the problem > Ralph
OK, so I went with Choice 2 and downloaded the nightly 2.0.3 from the 19th April. openmpi-v2.0.x-201704190318-24b5b83.tar.bz2 Having altered the top-level directory inside it to be just openmpi-2.0.x I then used that tarbal as a source for the SPEC file from 2.0.2's SRPM and ... it's all built and my application is now running inside the SGE environment. Deep joy ! Thanks for the suggestions, I'm looking forwards to the official releases of 2.0.3 and/or 2.1.1. Kevin _______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
