Ouch - sorry about that. pmix_setenv is actually defined down in the code base, so let me investigate why it got into pmix_common.
> On Jul 24, 2017, at 10:26 PM, George Bosilca <bosi...@icl.utk.edu> wrote: > > The last PMIX import broke the master on all platforms that support > visibility. I have pushed a patch that solves __most__ of the issues (that I > could find). I say most because there is a big left that require a > significant change in PMIX design. > > This problem arise from the use of the pmix_setenv symbol in one of the MCA > components (a totally legit operation). Except that in PMIX the pmix_setenv > is defined in opal/mca/pmix/pmix2x/pmix/include/pmix_common.h, which is one > of these headers that is self-contained and does not include the > config_bottom.h, and thus has no access to the PMIX_EXPORT. > > Here are 3 possible solutions: > 1. don't use pmix_setenv in any of the MCA components > 2. create a new header that provides support for all util functions (similar > to OPAL) and that supports PMIX_EXPORT > 3. make pmix_common.h not self-contained in order to provide access to > PMIX_EXPORT. > > Any of this approach requires changes to PMIX (and a push upstream). > Meanwhile the trunk seems to be broken on all platforms that support > visibility. > > George. > > > _______________________________________________ > devel mailing list > devel@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
