Bug #18763: The configure option “--with-openssl-dir” has lower precedence than pkg-config

• Status: Closed
• Assignee: rhenium (Kazuki Yamaguchi)
• Target version: -
• ruby -v: 2.7.6
• Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN

[franklinyu (Franklin Yu)]

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?

[franklinyu (Franklin Yu)]

• Description updated (diff)

[Eregon (Benoit Daloze)]

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.

[Eregon (Benoit Daloze)]

• Assignee set to rhenium (Kazuki Yamaguchi)

@rhenium (Kazuki Yamaguchi) I think we can close this once #18999 is done, right?

[Eregon (Benoit Daloze)]

• Related to Bug #18999: Backport openssl 2.1.4/2.2.2/3.0.1 added

[rhenium (Kazuki Yamaguchi)]

• Status changed from Open to Closed

Upstream issue for this bug: https://github.com/ruby/openssl/pull/486

Yes. This is resolved by openssl gem releases 2.1.4/2.2.2/3.0.1. Backporting is requested in #18999.