Project

General

Profile

Actions

Bug #18763

closed

The configure option “--with-openssl-dir” has lower precedence than pkg-config

Added by franklinyu (Franklin Yu) 9 months ago. Updated 5 months ago.

Status:
Closed
Priority:
Normal
Target version:
-
[ruby-core:108482]

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?


Related issues 1 (0 open1 closed)

Related to Ruby master - Bug #18999: Backport openssl 2.1.4/2.2.2/3.0.1ClosedActions
Actions #1

Updated by franklinyu (Franklin Yu) 9 months ago

  • Description updated (diff)

Updated by Eregon (Benoit Daloze) 9 months 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.

Updated by Eregon (Benoit Daloze) 5 months ago

  • Assignee set to rhenium (Kazuki Yamaguchi)

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

Actions #4

Updated by Eregon (Benoit Daloze) 5 months ago

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

Updated by rhenium (Kazuki Yamaguchi) 5 months ago

  • 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.

Actions

Also available in: Atom PDF

Like0
Like0Like0Like0Like0Like0