/usr/include is hardcoded in setup.py

[David Nyström]

Since /usr/include is hardcoded in setup.py, this makes cross compiling cumbersome.
I would suggest using automake to compile the C code, and let setup.py do the python stuff to adhere to common
interfaces.

[Paul Smith (psmith-gnu)]

I found this painful bug as well. However, automake etc. is completely unnecessary. A properly configured cross-compiler knows where to look for the proper cross-system headers and libraries. All you have to do is _never_ include any system header directories or library directories in your compile or link lines (never add -I/usr/include or -L/lib -L/usr/lib etc.), and when you run with the cross-compiler (just like any other compiler) it will automatically look for the right system headers in the right place.

Simply removing the '/usr/include' from the include_dirs list for Crypto.PublicKey._fastmath is the right answer.

[Richard Mitchell (mitchellrj)]

This was fixed in https://github.com/dlitz/pycrypto/commit/95918a1a86bc1e4c5045801b4bdb83359e033c6a#diff-2eeaed663bd0d25b7e608891384b7298

[Paul Smith (psmith-gnu)]

I just checked the latest pycrypto release 2.6.1 and it still appears that this patch from 2014 has not been applied... am I missing something?

[Paul Smith (psmith-gnu)]

Oh I see... there hasn't been a pycrypto release since 2013. That explains that, I suppose!!