This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author ned.deily
Recipients ned.deily, worldwise001
Date 2019-11-21.08:56:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1574326597.0.0.233578001891.issue38873@roundup.psfhosted.org>
In-reply-to
Content
How would having a "find the latest version" help here?  The point is Apple does not want you to use *any* version of libcrypto in /usr/lib: they are there only for old versions of third-party apps that were linked to a specific then-current version of the system libcrypto with a specific ABI.  For libssl and libcrypto, Apple has been saying for many releases you need to supply your own versions; they haven't been supplying the header files for them in the SDKs for several releases and now this.  If an app *is* trying to use an old version (which it shouldn't!), it does need to munge a specific version.
History
Date User Action Args
2019-11-21 08:56:37ned.deilysetrecipients: + ned.deily, worldwise001
2019-11-21 08:56:37ned.deilysetmessageid: <1574326597.0.0.233578001891.issue38873@roundup.psfhosted.org>
2019-11-21 08:56:36ned.deilylinkissue38873 messages
2019-11-21 08:56:36ned.deilycreate