extconf.rb - fixup to detect openssl info in Ruby build #3271
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
A common problem with gems that link to OpenSSL is determining which OpenSSL to use if the system has more than one version installed. One can use
--with-openssl-dir
, but we'd like to not require its use if possible.MRI Ruby may contain info in its
RbConfig::CONFIG['configure_args']
string that we can use to determine where OpenSSL is. Also, TruffleRuby often embeds the OpenSSL source.What often happens is that the code in
extconf.rb
finds theopenssl.pc
file, but it is for the wrong OpenSSL version.Update
extconf.rb
to take the above into account.Note that
--with-openssl-dir
is still available, which overrides everything.Closes #3266. Also see #2790, etc
Your checklist for this pull request
[ci skip]
to the title of the PR.#issue
" to the PR description or my commit messages.