Opened 3 years ago
Closed 3 years ago
#64259 closed defect (fixed)
mysql8 @8.0.27_4: wrong openssl command used
Reported by: | chrstphrchvz (Christopher Chavez) | Owned by: | herbygillot (Herby Gillot) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.7.1 |
Keywords: | Cc: | ||
Port: | mysql8 |
Description
I notice that during configure, this message is output:
-- The openssl command does not support zlib
This is not expected, as the openssl11 port does depend on zlib, and zlib
appears in the output of openssl-1.1 list -cipher-commands
. I am not sure whether this message means the build configuration is different or if it is merely informational.
This is caused by openssl
being hardcoded in the relevant CMake code (ssl.cmake), and the openssl
command in MacPorts is provided by the shim port which in turn uses openssl3 (and zlib
does not appear in the output of openssl-3 list -cipher-commands
); an openssl
command from the openssl11 port is not being used.
What would be a reasonable approach for having mysql8 use the correct openssl
command? Is it fine to just patch the hardcoded openssl
to openssl-[openssl::branch]
, or should [openssl::bin_dir]/openssl
be used somehow (e.g. prepend it to the PATH environment variable or an appropriate CMake variable, either from the Portfile or the openssl 1.0 PortGroup)?
Change History (1)
comment:1 Changed 3 years ago by herbygillot (Herby Gillot)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
In 810ceb79a534c5543d6d1c2dd37af52196bc3a09/macports-ports (master):