Today in "Shouldn't we be past this shite": trying to compile Python to use a non-system version of OpenSSL.

* Can get Python to compile and work, but it pulls in the system OpenSSL.
* Can get Python to compile, link against the non-system OpenSSL, but can't find libpython.
* Can get Python to compile, link against libpython, but is unable to find libssl/libcrypto


Have to say though - Docker really makes this kind of thing a lot easier than it used to be. Trying this in the past used to be way harder - when the environment is contaminated with leftovers from previous failed attempts, it can be hard to determine if your process will actually work in a clean system.

· · Web · 1 · 0 · 0

Following up on my Python build woes last week, I finally got it sort of working.

In the end it was trying to use libraries that were in both `/usr/local/lib` (for `libpython`) and `/usr/local/lib64` (for `libssl` and `libcrypto`), but my existing configuration for the Python build was only looking in `/usr/local/lib`.

Next step is to figure out why Python isn't building/installing to `/usr/local/lib64`.

Sign in to participate in the conversation
NI Tech

The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!