-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debian 9 Stretch Python 3.4.4 BUILD FAILED #945
Comments
This is probably due to Debian 9 using OpenSSL 1.1.0. OpenSSL 1.1.0 support in the |
Hmm. Actually we're applying some patches to |
+1... doesn't work with Python 3.4.7 either |
Has there been any movement on this? I'm trying to create a Docker image for running PySpark tests that extends from |
For reference this impacts Ubuntu bionic as well (since that's the first Ubuntu to get 1.1 which flowed from Debian stretch). |
there's two versions of openssl library and headers supplied by apt-get. |
Unfortunately in bionic installing the 1.0 dev version uninstalls the 1.1 dev version, and everything that depends on it, including npm / nodejs. |
I succeeded in building 3.4.8 on Debian Stretch while keeping the 1.1 headers. This is really a dirty workaround though, not a proper fix to this issue. As others have mentioned before, installing the 1.0 headers through apt doesn't work (unless you can live without the 1.1 headers). The two My workaround is simply to install the headers in a separate directory somewhere in my home directory. That's not a true installation, and most notably, package upgrades will have to be done manually. Download the libssl1.0-dev .deb (e.g. using
The libssl1.0-dev package contains two symlinks for libssl.so and libcrypto.so, and these don't point anywhere in that directory. We could "install"
Then, we need to tell Python about these files. This means setting a bunch of environment variables:
This will let it compile and install. There is no need to set an
|
* Fix travis configuration * Install Python versions in sequence When increased number of versions executed in parallel, the console is quiet for too long and causes travis-ci and hub.docker.com to timeout. * Adding missing dependencies * Drop 3.4.x Due to pyenv/pyenv#945 * Drop 3.4 * Drop 3.4
@JustAnotherArchivist do you think this workaround can somehow be included in the pyenv install script? I guess we could automatically download the header files in a temporary directory, compile the specified python version and afterwards clean the mess up. |
@Benestar, I think it could probably be done but might be quite tricky. |
Closing, as straightforward workarounds are available. |
I managed to install Python 3.4.10 on Fedora 30 (has OpenSSL 1.1+ by default) using following instructions:
|
I could fix the issue by appending |
@tillstud 's solution worked for me on Ubuntu 18.04 although I had to install libssl1.0-dev |
@tillstud Still works on Ubuntu 20 (focal) 🥳 |
Works on Debian Buster with |
Neither @JustAnotherArchivist or @tillstud's solution does not work on Ubuntu 21. |
Thank you @tillstud, This solution works on WSL(Ubuntu 20) |
On newer Ubuntu release
and manually extract, compile and install with it. |
These solutions don't work without permission to install the SSL packages, and not having these permissions was whole the reason I was using PyEnv in the first place to install Python |
@kmecpp you can build OpenSSL from source and point Python-build to it with envvars. |
With Debian 12 (bookworm) 1.1 is no longer available, using brew I was able to get everything working
|
I am having trouble getting Python 3.4.4 to install on Debian 9 Stretch. Here is what I have tried:
The text was updated successfully, but these errors were encountered: