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
This observation may not belong here, but as there are some eyes on this issue, I might as well raise it here, as I came across it in the wake of going with Choice 2 If one wishes to take a nightly tarball and try and use the existing version's SRPM build infrastructure to create an RPM, then you will fall foul of the dashes in the nightly tarball names. That is, if you try putting in Version: v2.0.x-201704190318-24b5b83 instead of the original Version: 2.0.2 you'll be told, when coming to do an rpmbuild, (your line may differ) error: line 188: Illegal char '-' in: Version: v2.0.x-201704190318-24b5b83 You can get round this by 1) Un-tar-ing the nightly tarball 2) Renaming it so that the dashes become dots 3) Recreating the newly named nightly tarball if you then use Version: v2.0.x.201704190318.24b5b83 the rpmbuild runs (as in it's running as I write !). As to whether that observation might inform a different convention for naming the nightly tarballs, that is left up to the real developers. _______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
