Re: _ssl.cpython-3.8.so does not exist in the tarball

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have another look at it.

On 07/10/2021 10:00, Michael Stahl wrote:
On 06.10.21 18:25, mcmurchy1917techy wrote:
Found my mistake.

I should have set the --enable-python flag in autogen  to system

that's not a mistake, the internal one ought to build, but it's not possible to figure out from the log why it failed:



Failed to build these modules:
_ssl


Could not build the ssl module!
Python requires an OpenSSL 1.0.2 or 1.1 compatible libssl with X509_VERIFY_PARAM_set1_host().
LibreSSL 2.6.4 and earlier do not provide the necessary APIs, https://github.com/libressl-portable/portable/issues/381

running build_scripts


On my system I ran

strings --print-file-name $(locate libssl) | grep X509_VERIFY_PARAM_set1_host

which returned


/lib/libssl.so.1.1: X509_VERIFY_PARAM_set1_host
/lib64/libssl.so.1.1: X509_VERIFY_PARAM_set1_host
/usr/lib/libssl.so: X509_VERIFY_PARAM_set1_host
/usr/lib/libssl.so.1.1: X509_VERIFY_PARAM_set1_host
/usr/lib64/libssl.so: X509_VERIFY_PARAM_set1_host
/usr/lib64/libssl.so.1.1: X509_VERIFY_PARAM_set1_host

So is it telling me that this python3 build is seeing X509_VERIFY_PARAM_set1_host at the beginning, but not at the end?

the error message appears to be generic - it's possible that the problem doesn't have anything to do with "X509_VERIFY_PARAM_set1_host".

perhaps there are more details further up in the log, or in a different log file.

also, the openssl may be used either internal or from the system, depending on --with-system-openssl/--with-system-libs.

[Index of Archives]     [LARTC]     [Bugtraq]     [Yosemite Forum]     [Photo]

  Powered by Linux