-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Compiling against different OpenSSL more complicated than in our docs #2006
Comments
There is no |
I had an issue with this the other day too, that started as a new feature in Tox which requires explicitly listing any environment variables you don't want to be scrubbed. pip has a |
@hynek - one trick you can use in the future is, in one terminal, |
Just to add key words that might help someone in future as this bit me also today – if you get something like "Symbol not found: _CRYPTO_malloc_debug_init" when trying to use cryptography, because you forgot to use the magic incantations when pip installing (or in my case, running tox) and using MacPorts, then as above you need to clear the wheel from your cache (in my case |
When compiling cryptography yourself if you have a problem and need to recompile but the wheel built successfully you need to know to clear the wheel cache. This is an edge case but worth documenting. Fixes pyca#2006
When compiling cryptography yourself if you have a problem and need to recompile but the wheel built successfully you need to know to clear the wheel cache. This is an edge case but worth documenting. Fixes pyca#2006
Since version 7, pip auto-wheels stuff caches it somewhere. That usually awesome.
But it brings problems too. So I’ve spent an hour yesterday trying desperately to recompile cryptography against my homebrew’s OpenSSL and I’ve failed. In the end I
pip install
ed my git checkout.I kept deleting stuff from my wheel house, tried to find caches but nothing. It always pulled it out of nowhere and
-v
didn’t help either. I’m gonna claim that if I’m too asinine to get this done, other people are likely too.This morning I found it out with the help of dtruss (concretely with it complaining, that I don’t own
/Users/hynek/Library/Caches/pip/http
b/c dtruss runs as root. So I killed all wheels there and got finally my juicy 1.0.2a.We need to update our docs in this regard, this is madness. Does pip have some
--force-recompile
option I’ve missed? If not, that should be filed there too…cc @dstufft
The text was updated successfully, but these errors were encountered: