2.6.1 build failure on OS X with clang

[Josiah Boning]

This is with pycrypto 2.6.1 from PyPI, and 2.6.x branch in git. Building from master seems to use gcc, so maybe this is moot?

cc -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch i386 -pipe -fno-common -fno-strict-aliasing -fwrapv -mno-fused-madd -DENABLE_DTRACE -DMACOSX -Wall -Wstrict-prototypes -Wshorten-64-to-32 -fwrapv -Wall -Wstrict-prototypes -DENABLE_DTRACE -arch x86_64 -arch i386 -pipe -std=c99 -O3 -fomit-frame-pointer -Isrc/ -I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -c src/MD2.c -o build/temp.macosx-10.9-intel-2.7/src/MD2.o

clang: error: unknown argument: '-mno-fused-madd' [-Wunused-command-line-argument-hard-error-in-future]

clang: note: this will be a hard error (cannot be downgraded to a warning) in the future

error: command 'cc' failed with exit status 1

$ cc --version
Apple LLVM version 5.1 (clang-503.0.38) (based on LLVM 3.4svn)
Target: x86_64-apple-darwin13.1.0
Thread model: posix

[Pablo Santiago Blum de Aguiar (scorphus)]

A temporary workaround:

$ CFLAGS=-Wunused-command-line-argument-hard-error-in-future pip install -U pycrypto

[Justin Riley (justin-t-riley)]

This explains the issue (Python uses same CFLAGS that it was originally built with when building extensions (which are now unsupported)):

http://stackoverflow.com/a/22315129

This provides a workaround for Python projects in setup.py until Apple provides updates to the system Python/Ruby installs:

http://stackoverflow.com/a/22931866