Bryce,
The current status on OS X is half baked, the /usr/bin/javah symlink is still there, but it points to nothing, and a direct consequence is that AC_PATH_PROG detects /usr/bin/javah, when I hope it does not. Since javac -h is already working in Java 8, I guess we do not care of older java versions. I am currently testing a PR that simply replace javah with javac -h Regarding the PR, you are obviously free to issue one. That being said, it should only be vs the master branch. Once it is merged, other PRs can be issued vs the release branches by cherry-picking (and back porting if needed) the commit in the master branch. This is how we work at Open MPI (e.g. no, we do not gitflow). Cheers, Gilles On Mon, Apr 2, 2018 at 8:48 AM, Bryce Glover <randomdsde...@gmail.com> wrote: > To Whom It May Concern: > > I’m currently putting together some pull-request content on a couple of > new branches on a fork of the ompi repository to resolve GitHub issue #5000 > (‘Open MPI Fails to Build Under OS X v10.11.6 ‘El Capitan’ Due to the > Absence of `java` in Java 10,’) which I submitted, myself (there are > actually two root problems at work there, so I’m addressing them > separately.) Am I thinking along the right sort of lines in my attempts to > go about staging my PRs? > > Curious, > Bryce Glover > randomdsde...@gmail.com > > _______________________________________________ > devel mailing list > devel@lists.open-mpi.org > https://lists.open-mpi.org/mailman/listinfo/devel _______________________________________________ devel mailing list devel@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/devel
