Skip to content

v3.0.x: Fix config/opal_setup_java.m4 from commit merged in #5119 #5161

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 10, 2018

Conversation

jsquyres
Copy link
Member

@jsquyres jsquyres commented May 9, 2018

That PR accidentally changed Open MPI's build configuration infrastructure's Java toolchain detection logic so that it would, as reported by @bosilca in #5001 (comment) and tracked down by me in #5001 (comment), abort your entire in-progress Open MPI build when it failed to find an OS X/macOS JDK instead of simply falling back to checking for a JDK in locations where it would be found on other platforms. Oops…!

Signed-off-by: Bryce Glover [email protected]
(cherry picked from commit 4a05c7e)

This is the v3.0.x version of the last java configury fix from #5160 (#5119 was already merged into v3.0.x branch, so I had to make a new PR for this one additional commit -- #5118 will include this PR when @ggouaillardet pulls it in).

     That PR accidentally changed Open MPI's build configuration infrastruc-
ture's Java toolchain detection logic so that it would, as reported by @bosilca
in open-mpi#5001 (comment) and tracked down by me in open-mpi#5001 (comment), abort your entire
in-progress Open MPI build when it failed to find an OS X/macOS JDK instead of
simply falling back to checking for a JDK in locations where it would be found
on other platforms.  _Oops…!_

Signed-off-by: Bryce Glover <[email protected]>
(cherry picked from commit 4a05c7e)
@jsquyres jsquyres added the bug label May 9, 2018
@jsquyres jsquyres added this to the v3.0.2 milestone May 9, 2018
@jsquyres jsquyres requested a review from ggouaillardet May 9, 2018 23:07
@jsquyres
Copy link
Member Author

jsquyres commented May 9, 2018

@bwbarrett @hppritcha This is a fix to a v3.0.x PR that was already merged (#5119). I checked: we did not include #5119 in the shipped v3.0.1, so we're ok -- both #5119 and this PR can be included in v3.0.2.

@RandomDSdevel FYI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants