Re: [OMPI devel] configure --with paths don't allow for absolute path specification

2017-09-02 Thread Phil K via devel
e: Phil, Did you simply try `--with-pmi` ? According to the configury macros, we look for /usr/include/pmi.h and then /usr/include/slurm/pmi.h, so that should work just fine. If not, can you please compress and post your config.log ? Cheers, Gilles Phil K via devel wrote: Exactly. 

Re: [OMPI devel] configure --with paths don't allow for absolute path specification

2017-09-02 Thread Phil K via devel
PMI header you want - so long as you then link your code to a PMIx library, it doesn’t matter if that header differs somewhat from the one we use. All that matters is that any function call you use matches the one we wrote against. We took ours directly from the MPICH official ones. Ralph On

Re: [OMPI devel] configure --with paths don't allow for absolute path specification

2017-09-02 Thread Phil K via devel
y from the MPICH official ones. Ralph On Sep 1, 2017, at 10:08 PM, Phil K via devel wrote: I just wanted to share a workaround I came up with for this openmpi configure issue. When specifying header paths in configure, openmpi adds an /include subpath the --with-pmi specifier(and others)

[OMPI devel] configure --with paths don't allow for absolute path specification

2017-09-01 Thread Phil K via devel
I just wanted to share a workaround I came up with for this openmpi configure issue. When specifying header paths in configure, openmpi adds an /include subpath the --with-pmi specifier(and others).  This is documented very clearly.  Recently, in switching over to internal pmix, I wanted to rip