You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If MPICH is configured with an external PMIx library using
--with-pmix=<path to pmix lib>
and in addition MPICHs built-in PMI1/2 support is enabled via --with-pmilib=mpich
the wrong PMIx header file is used at compile time. It uses src/pmi/include/pmix.h instead of the header provided in <path to pmix lib>.
Is there a combination of MPICH configure options that can prevent this?
Could this be fixed by, for example, changing src/pmi/Makefile.am to exclude all the pmix* files in src/pmi/ from compilation when an external PMIx lib is configured? Or do the pmix* files (at least the headers) have to get their own subdirectory to avoid naming clashes for pmix.h?
Thank you! :)
The text was updated successfully, but these errors were encountered:
Ahh, the issue is we have pmix.h in the same path as pmi.h and pmi2.h, so the include path src/pmi/include clobbered the <path to pmix lib>. May be we can move our internal pmix.h to a subfolder.
If MPICH is configured with an external PMIx library using
--with-pmix=<path to pmix lib>
--with-pmilib=mpich
the wrong PMIx header file is used at compile time. It uses
src/pmi/include/pmix.h
instead of the header provided in<path to pmix lib>
.Is there a combination of MPICH configure options that can prevent this?
Could this be fixed by, for example, changing
src/pmi/Makefile.am
to exclude all thepmix*
files insrc/pmi/
from compilation when an external PMIx lib is configured? Or do thepmix*
files (at least the headers) have to get their own subdirectory to avoid naming clashes forpmix.h
?Thank you! :)
The text was updated successfully, but these errors were encountered: