Bug #18763
openThe configure option “--with-openssl-dir” has lower precedence than pkg-config
Description
I’m trying to compile Ruby 2.7.6 (latest stable release in 2.7 branch). In my environment, there are two OpenSSL installed, v1.1 and v3. The system pkg-config will find OpenSSL v3, but it isn’t compatible with Ruby 2.7, so I’d like to configure Ruby to link to OpenSSL v1.1 with --with-openssl-dir
, but ./configure
still uses OpenSSL 3 (that it found via pkg-config). Is this expected? If so, how am I supposed to override the OpenSSL directory?
Updated by franklinyu (Franklin Yu) about 2 months ago
- Description updated (diff)
Updated by Eregon (Benoit Daloze) about 1 month ago
This issue has more details: https://github.com/postmodern/ruby-install/issues/412
So CRuby picks a mix of of 1.1 headers and 3.0 lib, when given --with-openssl-dir
.
That sounds like a clear bug.
Setting PKG_CONFIG_PATH
helps but this is not intuitive, --with-openssl-dir
should be enough on its own.