[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]

#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:16 mouse07410]:
 > > > To summarize: please reconsider.
 > >
 > > No. The only reason we are discussing this is because the OPs ports
 where not up to date.
 >
 > This is **not** only about Macports ports. It's about tons of user-
 installed apps that require OpenSSL, and chose to rely upon Macports-
 provided OpenSSL.
 >
 > > Just putting the 1.1 libraries into the primary prefix would not be
 enough. Any port wanting to build against openssl 1.1 would need to find
 the headers
 >
 > Again, you're talking about ports (as if no other software existed). I'm
 talking about a pile of **existing installed binaries** - **not ports** -
 that suddenly stopped working. Some of them may not be easy to rebuild.

 *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. Most rebuilt just fine against openssl3. The handful that
 have not nbeed to be addressed. Again, this was totally expected. Fixing
 them all *before* the migration was not practical, so this was the
 pragmatic approach.

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