vincent.vandevy...@oqapy.eu writes:
>> In case this helps you find the correct package to install:
>>
>> $ python3 -c "if True:
>> > import ssl
>> > print('Ok.')
>> > "
>> Ok.
>>
>> $ cat /etc/lsb-release
>> DISTRIB_ID=Ubuntu
>> DISTRIB_RELEASE=24.04
>> DISTRIB_CODENAME=noble
>> DISTRIB_DESCRIPTION="Ubuntu 24.04.1 LTS"
>>
>> $ apt list --installed | grep ssl
>>
>> WARNING: apt does not have a stable CLI interface. Use with caution in
>> scripts.
>>
>> libssl-dev/noble-updates,noble-security,now 3.0.13-0ubuntu3.4 amd64
>> [installed]
>> libssl3t64/noble-updates,noble-security,now 3.0.13-0ubuntu3.4 amd64
>> [installed,automatic]
>> libxmlsec1t64-openssl/noble,now 1.2.39-5build2 amd64 [installed,automatic]
>> openssl/noble-updates,noble-security,now 3.0.13-0ubuntu3.4 amd64
>> [installed,automatic]
>> ssl-cert/noble,noble,now 1.1.2ubuntu1 all [installed,automatic]
>
> Thanks Jason, I have near the same result of you.
> I need to explain the context.
> I'm on a new machine with a fresh install of Ubuntu 24.04 wich embed Python
> 3.12.3, no problem with that.
>
> As I'm maintainer of some Python modules published on PyPI, I've the
> habit of testing my modules in different virtual environments. For now
> Python 3.11, 3.12 and 3.13.
>
> So, I've maybe found a solution:
>
> I've create in my home a dir named /opt, download into it the latest version
> of openssl-1.1.1 and uncompress it.(*)
> -------------------------------------------------------------
> $ cd opt/openssl-1.1.1w
> $ ./config && make && make test
> $ mkdir $HOME/opt/lib
> $ mv $HOME/opt/openssl-1.1.1w/libcrypto.so.1.1 $HOME/opt/lib/
> $ mv $HOME/opt/openssl-1.1.1w/libssl.so.1.1 $HOME/opt/lib/
> $ export LD_LIBRARY_PATH=$HOME/opt/lib:$LD_LIBRARY_PATH
> --------------------------------------------------------------
> And rerun the compilation of 3.12.9 without problem with openssl.
>
> (*) https://openssl-library.org/source/old/1.1.1/index.html
OpenSSL 1.1.1 is pretty old, released in 2018 if I'm not mistaken.
An environment on Ubuntu 24.04 with OpenSSL 1.1.1 libraries is a bit
unusual. If your goal is to ensure that you can build Python with the
oldest OpenSSL it claims to support, what you're doing makes sense. But
if you have libssl-dev already installed and your Python build complains
"Python requires a OpenSSL 1.1.1 or newer", then something weird is
going on, and it's probably worth tracking it down. The best solution
*should* be to install the current libssl-dev package from the package
manager, not to build an old version of OpenSSL from source.
I've built Python-3.12.9 from source on Ubuntu-22.04 with no problems
(I have libssl-dev installed).
To be clear, what is the output of "dpkg -l libssl-dev" on your Ubuntu
24.04 system? If you get something similar to this:
```
$ dpkg -l libssl-dev
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-================-==============-============-================================================
ii libssl-dev:amd64 3.3.1-2ubuntu2 amd64 Secure Sockets Layer toolkit -
development files
```
then I don't understand why you'd get the "Python requires a OpenSSL
1.1.1 or newer" message.
--
Keith Thompson (The_Other_Keith) keith.s.thompso...@gmail.com
void Void(void) { Void(); } /* The recursive call of the void */
--
https://mail.python.org/mailman/listinfo/python-list
