From: "Eregon (Benoit Daloze)" Date: 2022-05-11T11:39:05+00:00 Subject: [ruby-core:108508] [Ruby master Bug#18763] The configure option “--with-openssl-dir” has lower precedence than pkg-config Issue #18763 has been updated by 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. ---------------------------------------- Bug #18763: The configure option ���--with-openssl-dir��� has lower precedence than pkg-config https://bugs.ruby-lang.org/issues/18763#change-97552 * Author: franklinyu (Franklin Yu) * Status: Open * Priority: Normal * ruby -v: 2.7.6 * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN ---------------------------------------- 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? -- https://bugs.ruby-lang.org/ Unsubscribe: