Actually, I take that back - making a separate PR to change the opal/pmix embedded component to a submodule was way too painful. I simply added it to the existing #7202.
> On Jan 7, 2020, at 1:33 PM, Ralph Castain via devel > <devel@lists.open-mpi.org> wrote: > > Just an FYI: there will soon be THREE PRs introducing submodules - I am > breaking #7202 into two pieces. The first will replace opal/pmix with direct > use of PMIx everywhere and replace the embedded pmix component with a > submodule pointing to PMIx master, and the second will replace ORTE with > PRRTE. > > >> On Jan 7, 2020, at 9:02 AM, Jeff Squyres (jsquyres) via devel >> <devel@lists.open-mpi.org> wrote: >> >> We now have two PRs pending that will introduce the use of Git submodules >> (and there are probably more such PRs on the way). At last one of these >> first two PRs will likely be merged "Real Soon Now". >> >> We've been talking about using Git submodules forever. Now we're just about >> ready. >> >> ************************************** >> *** DEVELOPERS: THIS AFFECTS YOU!! *** >> ************************************** >> >> You cannot just "clone and build" any more: >> >> ----- >> git clone g...@github.com:open-mpi/ompi.git >> cd ompi && ./autogen.pl && ./configure ... >> ----- >> >> You will *have* to initialize the Git submodule(s) -- either during or after >> the clone. *THEN* you can build Open MPI. >> >> Go read this wiki: https://github.com/open-mpi/ompi/wiki/GitSubmodules >> >> May the force be with us! >> >> -- >> Jeff Squyres >> jsquy...@cisco.com >> > >