Message218843
Unfortunately this patch will not work if there is other (system) openssl installed in the default locations (`/usr/include`, `/usr/lib`) because this patch only add another path at the end of the search list.
Instead of this I will make a ticket for providing configuration option for controlling the `openssl` (`--with-ssl=PATH`) and I will propose the solution (patch for current `configure` and `setup.py`). This way the user can explicitly provide the path for `openssl` and there is no need to search for one.
I think it is important to fix this because there is a lot of people having problem compiling `python` with custom `openssl`, eg.: [http://stackoverflow.com/questions/22409092/coredump-when-compiling-python-with-a-custom-openssl-version] |
|
Date |
User |
Action |
Args |
2014-05-20 13:29:49 | machyniak | set | recipients:
+ machyniak, collinwinter, jafo, isandler, pitrou, eric.araujo, ikeaxial |
2014-05-20 13:29:49 | machyniak | set | messageid: <1400592589.28.0.979216738078.issue5575@psf.upfronthosting.co.za> |
2014-05-20 13:29:49 | machyniak | link | issue5575 messages |
2014-05-20 13:29:47 | machyniak | create | |
|