[MacPorts] #63876: openssl3 @ 3.0.0_2+universal.darwin_15.i386-x86_64: dyld: Library not loaded: /opt/local/lib/libcrypto.1.1.dylib
MacPorts
noreply at macports.org
Wed Nov 10 16:40:55 UTC 2021
#63876: openssl3 @ 3.0.0_2+universal.darwin_15.i386-x86_64: dyld: Library not
loaded: /opt/local/lib/libcrypto.1.1.dylib
-----------------------+---------------------------------
Reporter: thetrial | Owner: larryv
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 2.7.1
Resolution: fixed | Keywords: elcapitan legacy-os
Port: openssl3 |
-----------------------+---------------------------------
Comment (by mouse07410):
> The only reason we are discussing this is because the OPs ports where
not up to date.
No! That's just one symptom - there are plenty more of these. For me, the
majority (surprisingly!) are **not** Macports-installed.
We're discussing this because now with one quick change all of the
binaries (including those **not** installed by Macports!) that were ever
linked with OpenSSL-1.1.1, stopped working. It is impractical to expect a
normal user to suddenly become a full-time sysadmin who goes through the
apps one by one, reconfiguring and rebuilding them until everything starts
working again.
To remind: one reason people turn to Macports is exactly to avoid having
to do a lot of heavy lifting on their own.
> not when the user keeps their ports up to date, and when ports correctly
use the openssl PG to build against specific older versions.
Again and again - OpenSSL is a port that provides services to pretty much
all the apps and libraries that require OpenSSL on Mac, partially because
you can't even link against LibReSSL version that comes with MacOS. So,
breaking it you not only (temporarily) break some ports - you break **all
the other user-installed software**.
A lot of that software uses {{{pkg-config}}} to locate OpenSSL. So far, it
was not able to locate OpenSSL-1.1.1 in libexec - special instructions are
necessary.
> *all* existing binaries indeed need to be rebuilt. This is (was)
expected. All ports where in fact rev-bump when openssl3 was made the
default for the very reason.
I'm afraid I'm not making myself clear enough. You seem to be talking
exclusively about ports...?
> Most rebuilt just fine against openssl3
Unfortunately, outside of ports themselves, this is wrong - some do, and
some don't.
> so this was the pragmatic approach.
I concur with everything except for not symlinking 1.1 libs into the
primary prefix.
OK, I don't think I've explained the situation clearly enough to convince
you. Fine. Thankfully, manual symlinking works, and if that approach
contradicts your wisdom - I'd have to live with that.
--
Ticket URL: <https://trac.macports.org/ticket/63876#comment:21>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list