Skip to content
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

Remove strict openssl@1.1 requirement from TruffleRuby, jruby-dev definitions #2278

Merged
merged 2 commits into from
Oct 20, 2023

Conversation

mislav
Copy link
Member

@mislav mislav commented Oct 20, 2023

TruffleRuby build definitions used to explicitly rely on brew --prefix openssl@1.1 on macOS and abort installation if that was not found. However, this check didn't take into account that the user might have set OPENSSL_PREFIX in their environment, or that they have another openssl@* version installed via Homebrew. This change removes the use_homebrew_openssl check and allows TruffleRuby to perform its own OpenSSL detection.

From #2275 (comment)

TruffleRuby build definitions used to explicitly rely on `brew --prefix openssl@1.1` on macOS and abort installation if that was not found. However, this check didn't take into account that the user might have set OPENSSL_PREFIX in their environment, or that they have another `openssl@*` version installed via Homebrew. This change removes the `use_homebrew_openssl` check and allows TruffleRuby to perform its own OpenSSL detection.

https://github.com/oracle/truffleruby/blob/vm-23.1.0/lib/truffle/truffle/openssl-prefix.rb#L14-L17
This is to allow JRuby itself to check for compatible OpenSSL versions and not have ruby-build abort early on macOS.
@mislav mislav requested a review from eregon October 20, 2023 12:03
@eregon eregon merged commit 99fda28 into master Oct 20, 2023
6 checks passed
@eregon eregon deleted the truffleruby-jruby-no-openssl branch October 20, 2023 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants