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

[mcmurchy1917techy]

Found my mistake.

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

Apologies for the noise.

Alex

On 30/09/2021 10:14, mcmurchy1917techy wrote:
>
> Hi Michael
>
> Thanks for the reply
>
> The build.log for python3 contains
>
>> checking whether compiling and linking against OpenSSL works... yes
>> checking for X509_VERIFY_PARAM_set1_host in libssl... yes
>> checking for --with-ssl-default-suites... python
>> configure: creating ./config.status
>> config.status: creating Makefile.pre
>> config.status: creating Misc/python.pc
>> config.status: creating Misc/python-embed.pc
>> config.status: creating Misc/python-config.sh
>> config.status: creating Modules/ld_so_aix
>> config.status: creating pyconfig.h
>> creating Modules/Setup.local
>> creating Makefile
>>
>>
>> If you want a release build with all stable optimizations active (PGO, etc),
>> please run ./configure --enable-optimizations
>>
>>
>> make[2]: Entering directory '/home/master/master/workdir/UnpackedTarball/python3'
>
> after a short while it fails with
>
>> The following modules found by detect_modules() in setup.py, have been
>> built by the Makefile instead, as configured by the Setup files:
>> _abc                  atexit                pwd
>> time
>>
>>
>> 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?
>
> Alex
>
>
> On 29/09/2021 09:41, Michael Stahl wrote:
>> On 27.09.21 08:52, mcmurchy1917techy wrote:
>>> Did a pull over the weekend.
>>>
>>> Compiled and got this error.
>>>
>>>> [build DEP] LNK:Library/libcuilo.so
>>>> [build DEP] LNK:Library/libcuilo.so
>>>> [build LNK] Library/libcuilo.so
>>>> /home/master/master/external/python3/ExternalPackage_python3.mk:46: *** file 
>>>> /home/master/master/workdir/UnpackedTarball/python3/LO_lib/_ssl.cpython-3.8.so does not exist in the tarball.  Stop.
>>>> make[1]: *** Waiting for unfinished jobs....
>>>> make: *** [Makefile:288: build] Error 2
>>
>> the problem is that python's configure equivalent is far too magical in nature and will auto-detect what dependencies 
>> it can find and then enable the corresponding modules.
>>
>> for some reason the internal python cannot find the OpenSSL library (either on system or internal, depending on 
>> --with-system-openssl) and thus it did not build the ssl module and the earliest point where we can detect failure is 
>> that the file doesn't exsit when trying to copy it to instdir.
>>
>>> My autogen has this flag --enable-python=internal. If I remove the flag --enable-python=internal libreoffice 
>>> compiles successfully.
>>>
>>> I'm a bit behind the curve, the last time I compiled was June 12th also with  --enable-python=internal, that was 
>>> successful
>>>
>>> What do I need to do to resolve?
>>
>> try to figure out from the workdir/UnpackedTarball/python3/build.log why OpenSSL isn't found.
>>
>>> My system has the python3 3.9.6 package. Have I got myself ahead of the curve?
>>
>> that should be unrelated.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/libreoffice/attachments/20211006/1b8a4201/attachment.htm>