[MacPorts] #63550: ruby26 @2.6.8_2 and ruby30 @3.0.2_1 build fails against openssl v3.0.0

MacPorts noreply at macports.org
Sun Oct 3 03:08:20 UTC 2021


#63550: ruby26 @2.6.8_2 and ruby30 @3.0.2_1 build fails against openssl v3.0.0
------------------------------------+--------------------
  Reporter:  kencu                  |      Owner:  (none)
      Type:  defect                 |     Status:  new
  Priority:  Normal                 |  Milestone:
 Component:  ports                  |    Version:
Resolution:                         |   Keywords:
      Port:  ruby26 ruby30 openssl  |
------------------------------------+--------------------

Comment (by fhgwright):

 When I was working on `ruby??` last year, I ran into a build problem with
 `ruby22` on 10.15 related to its use of `openssl10`.  I partially
 investigated, and found that the problem was that, even though the path to
 `openssl10` was being supplied explicitly in the `configure` args, there
 was still something in the build procedure that was using `pkg-config` to
 locate `openssl`, and finding the standard one instead of the alternate.
 With the `openssl` port active, this resulted in its trying to build with
 a mixture of `openssl` versions, and failing due to incompatibilities.
 With the `openssl` port inactive, the build would succeed, but examination
 of `config.log` showed that it had internally disabled `openssl` support.
 This is a silent failure that would go unnoticed until someone actually
 tried to use some `ruby` feature dependent on `openssl`.  The build
 failure would never show up in a CI test, since the CI setup doesn't
 activate non-dependencies.

 I have no idea why it only showed up under 10.15, or why it didn't affect
 `ruby23` (which also uses `openssl10`), but that's what I saw.  I was able
 to fix it by defining `PKG_CONFIG_PATH` to point to the `openssl10`
 location, but there was some other unresolved issue that kept me from
 pushing the fix.

 Around that  time, I decided to punt on further `ruby??` work, but it's
 something that needs further investigation, especially if usage of
 alternate `openssl` versions becomes more common.

-- 
Ticket URL: <https://trac.macports.org/ticket/63550#comment:13>
MacPorts <https://www.macports.org/>
Ports system for macOS


More information about the macports-tickets mailing list