It apparently did come in that way. We just never test -no-ompi and so it wasn’t discovered until a downstream project tried to update. Then...boom.
> On Jun 22, 2017, at 4:07 PM, Barrett, Brian via devel > <devel@lists.open-mpi.org> wrote: > > I’m confused; looking at history, there’s never been a time when > opal/util/info.c hasn’t included mpi.h. That seems odd, but so does info > being in opal. > > Brian > >> On Jun 22, 2017, at 3:46 PM, r...@open-mpi.org wrote: >> >> I don’t understand what someone was thinking, but you CANNOT #include >> “mpi.h” in opal/util/info.c. It has broken pretty much every downstream >> project. >> >> Please fix this! >> Ralph >> >> _______________________________________________ >> 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 _______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
