On 21/10/15 09:48, Cory Benfield wrote:
> 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
On 21/10/15 03:18, Erik Trauschke wrote:
> I would add a run path to your LDFLAGS, this way you can be sure it
> picks up the correct OpenSSL library if your library search paths are
> not set to the right value by crle or things like LD_LIBRARY_PATH.
>
> You can do that by adding -R/path/to/lib t
> On 21 Oct 2015, at 01:40, Jesus Cea 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
I would add a run path to your LDFLAGS, this way you can be sure it
picks up the correct OpenSSL library if your library search paths are
not set to the right value by crle or things like LD_LIBRARY_PATH.
You can do that by adding -R/path/to/lib to LDFLAGS.
Erik
On Tue, Oct 20, 2015 at 5:40 PM,
