Use pkg-config for determining the OpenSSL path instead of using /usr/local by default under Linux #120
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.
Pretty much any modern Linux distribution is using
pkg-config
these days to share a few common details about the way packages are configured and installed on the host system. Theopenssl
package (at least under Ubuntu/Debian) exposes the prefix it is installed under with theprefix
variable inpkg-config
.These modifications are using
pkg-config
to determine the prefix foropenssl
.Using
/usr/local
as a default will fail to build Ruby with OpenSSL support, "silently" (it's just not detected at compile time), with the symptom simply being that any Ruby built withfrum
won't have TLS/SSL support. This is especially relevant for the latest Ubuntu release (22.04, Jammy Jellyfish) since it ships with OpenSSL 3.x for which there currently is no support in the OpenSSL gem.