[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:16:29 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 cjones051073):

 Replying to [comment:9 mouse07410]:
 > > The openssl11 port intentionally does not install anything in the
 primary prefix. It *only* installs to its isolated install area under
 libexec. Any build using openssl11 neds to be configured to use the
 libraries from that area
 >
 > Respectfully disagree.
 >
 > {{{openssl11}}} and {{{openssl3}}} must co-exist, at least for some
 time. It makes perfect sense to make both available in the "main" Macports
 library dir {{{/opt/local/lib}}}. Especially since there are plenty of
 (non-Macports) apps that cannot (yet?) switch to OpenSSL-3.0. E.g., I've
 been linking my stuff that uses OpenSSL against Macports-installed OpenSSL
 for ages.
 >
 > The whole reason for "dotted" versions for {{{.dylib}}} is to support
 exactly this: safely having {{{libssl.1.1.dylib}}} and
 {{{libssl.3.dylib}}} in the same directory.
 >
 > To summarize: please reconsider.

 No. The only reason we are discussing this is because the OPs ports where
 not up to date.

 Any port now requiring openssl11 must either use the openssl PG, which
 will (help to) configure the build correctly to link against the libexec
 install area, or (not really recommended) do this by hand. The openssl
 shim port make links into the primary prefix to make that version
 available. Thats all, the older versions are intentionally left isolated
 under libexec.

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


More information about the macports-tickets mailing list