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 christian.heimes
Recipients Phillip Middleton, bkline, cayman, chris.jerdonek, christian.heimes, cstratak, fthommen, hairygristle, kscheidegger, malektronic, simon@simonfoley.net
Date 2019-10-24.10:10:09
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1571911809.92.0.536541792027.issue34028@roundup.psfhosted.org>
In-reply-to
Content
--with-openssl only sets the header location for the pre-processor and library path for the dynamic linker. It does *not* affect the search and lookup paths of the dynamic loader! If you have installed OpenSSL in a non-standard location then you need to tell the dynamic loader how to load the shared libraries. This can be done in three ways:

* configure the dynamic loader globally in /etc/ld.so.conf (not advised for custom OpenSSL)
* Add a rpath to the ELF header of _ssl and _hashlib extensions at link time. This can be accomplished by setting LD_RUN_PATH=/path/to/lib or LDFLAGS=-Wl,-rpath,/path/to/lib
* Add the shared library directory to the runtime lookup path of ld.so by setting LD_LIBRARY_PATH env var.
History
Date User Action Args
2019-10-24 10:10:09christian.heimessetrecipients: + christian.heimes, bkline, chris.jerdonek, cstratak, hairygristle, simon@simonfoley.net, fthommen, kscheidegger, Phillip Middleton, cayman, malektronic
2019-10-24 10:10:09christian.heimessetmessageid: <1571911809.92.0.536541792027.issue34028@roundup.psfhosted.org>
2019-10-24 10:10:09christian.heimeslinkissue34028 messages
2019-10-24 10:10:09christian.heimescreate