> On 21 Oct 2015, at 01:40, Jesus Cea <j...@jcea.es> wrote: > > My stock OpenSSL library is ancient so I installed an alternative > current OpenSSL release under "/usr/local/ssl". In order to compile > "cryptography" in this machine I must do: > > $ LDFLAGS="-L/usr/local/ssl/lib" \ > CFLAGS="-I/usr/local/ssl/include" \ > python -m pip install -U cryptography > > This is a Solaris machine, but I guess the same can be done in Linux, > and other unix-like OSs. > > Please, add something about this in > <https://cryptography.io/en/latest/installation/>.
We’re already very close to this: the instructions in the ‘static wheels’ section of the documentation[0], while slightly more complicated, include the LDFLAGS and CFLAGS notation. The OS X section includes it as well. I wonder if we need to extend the “using your own OpenSSL on Linux” section [1] to include the LDFLAGS and CFLAGS. [0]: https://cryptography.io/en/latest/installation/#static-wheels [1]: https://cryptography.io/en/latest/installation/#using-your-own-openssl-on-linux > PS: How can I know what OpenSSL version is using "cryptography", beside > checking the loaded shared objects by hand? :): Try this: $ python -c "from cryptography.hazmat.backends.openssl.backend import backend;print(backend.openssl_version_text())” Cory
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Cryptography-dev mailing list Cryptography-dev@python.org https://mail.python.org/mailman/listinfo/cryptography-dev
