> On Apr 25, 2018, at 8:16 AM, Michael Di Domenico <mdidomeni...@gmail.com> > wrote: > > On Mon, Apr 23, 2018 at 6:07 PM, r...@open-mpi.org <r...@open-mpi.org> wrote: >> Looks like the problem is that you didn’t wind up with the external PMIx. >> The component listed in your error is the internal PMIx one which shouldn’t >> have built given that configure line. >> >> Check your config.out and see what happened. Also, ensure that your >> LD_LIBRARY_PATH is properly pointing to the installation, and that you built >> into a “clean” prefix. > > the "clean prefix" part seemed to fix my issue. i'm not exactly sure > i understand why/how though. i recompiled pmix and removed the old > installation before doing a make install
When you build, we don’t automatically purge the prefix location of any prior libraries. Thus, the old install of the internal PMIx library was still present. It has a higher priority than the external components, and so it was being picked up and used. Starting clean removed it, leaving the external component to be selected. > > when i recompiled openmpi it seems to have figured itself out > > i think things are still a little wonky, but at least that issue is gone > _______________________________________________ > users mailing list > users@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/users _______________________________________________ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
