Re: [OMPI devel] PMI2 in Slurm 14.11.8
On 02/09/15 13:09, Christopher Samuel wrote: > Instead PMI2 is in a contrib directory which appears to need manual > intervention to install. Confirming from the Slurm list that PMI2 is not built by default, it's only the RPM build process that will include it without intervention. Thanks for your help Ralph! cheers, Chris -- Christopher SamuelSenior Systems Administrator VLSCI - Victorian Life Sciences Computation Initiative Email: sam...@unimelb.edu.au Phone: +61 (0)3 903 55545 http://www.vlsci.org.au/ http://twitter.com/vlsci
[OMPI devel] 1.10.0 issue
Hi folks I regret to say that 1.10.0 is hitting an issue with at least one upstream distro. Apparently, there is a symbol conflict between the PSM and PSM2 libraries that precludes building both of those MTLs at the same time. This is leading the distro to push for release of two OMPI 1.10.0 builds - one with PSM and the other with PSM2. IMO, this is a very undesirable situation. I agree with the distro that delaying release for some significant time as this would impact everyone else’s users. Therefore, assuming that the PSM team is unable to quickly resolve the problem in their libraries, my inclination is to release an immediate 1.10.1 with the PSM2 MTL removed. I’m soliciting input - any opinions? Ralph
Re: [OMPI devel] 1.10.0 issue
Ralph, what about automatically *not* building PSM2 if PSM is built and PSM2 is not explicitly required ? /* in order to be future proof, we could even do that only if we detect a symbol conflict */ we could abort if ompi is configure'd with both --with-psm and --with-psm2, or simply do nothing (the end user might know what he/she is doing, and there will be nothing to do on the ompi side when this gets fixed by the PSM folks) Cheers, Gilles On 9/3/2015 10:21 AM, Ralph Castain wrote: Hi folks I regret to say that 1.10.0 is hitting an issue with at least one upstream distro. Apparently, there is a symbol conflict between the PSM and PSM2 libraries that precludes building both of those MTLs at the same time. This is leading the distro to push for release of two OMPI 1.10.0 builds - one with PSM and the other with PSM2. IMO, this is a very undesirable situation. I agree with the distro that delaying release for some significant time as this would impact everyone else’s users. Therefore, assuming that the PSM team is unable to quickly resolve the problem in their libraries, my inclination is to release an immediate 1.10.1 with the PSM2 MTL removed. I’m soliciting input - any opinions? Ralph ___ devel mailing list de...@open-mpi.org Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel Link to this post: http://www.open-mpi.org/community/lists/devel/2015/09/17919.php
Re: [OMPI devel] 1.10.0 issue
I’m afraid that won’t solve the problem - the distro will still feel the need to release -two- versions of OMPI, one with PSM and one with PSM2. Ordinarily, I wouldn’t care - but this creates user confusion and reflects on us as a community. > On Sep 2, 2015, at 6:50 PM, Gilles Gouaillardet wrote: > > Ralph, > > what about automatically *not* building PSM2 if PSM is built and PSM2 is not > explicitly required ? > /* in order to be future proof, we could even do that only if we detect a > symbol conflict */ > we could abort if ompi is configure'd with both --with-psm and --with-psm2, > or simply do nothing > (the end user might know what he/she is doing, and there will be nothing to > do on the ompi side > when this gets fixed by the PSM folks) > > Cheers, > > Gilles > > On 9/3/2015 10:21 AM, Ralph Castain wrote: >> Hi folks >> >> I regret to say that 1.10.0 is hitting an issue with at least one upstream >> distro. Apparently, there is a symbol conflict between the PSM and PSM2 >> libraries that precludes building both of those MTLs at the same time. This >> is leading the distro to push for release of two OMPI 1.10.0 builds - one >> with PSM and the other with PSM2. >> >> IMO, this is a very undesirable situation. I agree with the distro that >> delaying release for some significant time as this would impact everyone >> else’s users. Therefore, assuming that the PSM team is unable to quickly >> resolve the problem in their libraries, my inclination is to release an >> immediate 1.10.1 with the PSM2 MTL removed. >> >> I’m soliciting input - any opinions? >> Ralph >> >> ___ >> devel mailing list >> de...@open-mpi.org >> Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel >> Link to this post: >> http://www.open-mpi.org/community/lists/devel/2015/09/17919.php > > ___ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/09/17920.php
