[MacPorts] #72186: cfengine3 @3.18.0: unknown type name 'RSA' and call to undeclared function 'RSA_get0_key';
MacPorts
noreply at macports.org
Thu Mar 13 08:12:19 UTC 2025
#72186: cfengine3 @3.18.0: unknown type name 'RSA' and call to undeclared function
'RSA_get0_key';
------------------------+--------------------
Reporter: kwolcott | Owner: (none)
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: cfengine3 |
------------------------+--------------------
Changes (by ryandesign):
* cc: cjones051073 (added)
Comment:
I've spent at least an hour trying to fix this unsuccessfully. It's too
difficult to get a port to use the non-default openssl version.
`-I/opt/local/include` and `-L/opt/local/lib` still end up in the build's
CPPFLAGS and LDFLAGS, respectively, before the flags for the desired
openssl directory. (I don't mean the environment variables MacPorts sets;
I mean the flags that end up being used by the build, which are a
combination of MacPorts-specified flags and its own flags.) The openssl
portgroup also adds `-isystem/opt/local/include`, ensuring that the
headers in /opt/local/include are searched after the ones in the openssl
path, even if `-I/opt/local/include` appears before the flag for the
openssl path. Unfortunately, no equivalent exists for `-L` flags, so it
links with the openssl 3 library in /opt/local/lib which of course fails
since it doesn't have the symbols the openssl 1.1 headers described.
Someone who understands the openssl portgroup better needs to finish this,
possibly including enhancing the openssl portgroup or ports to make this
easier, though I don't know how.
--
Ticket URL: <https://trac.macports.org/ticket/72186#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list