clang error: unknown argument: '-mno-fused-madd' (python package installation failure)
You can tell clang to not raise this as an error by setting the following environment variables prior compilation:
export CFLAGS=-Qunused-argumentsexport CPPFLAGS=-Qunused-arguments
pip install psycopg2should work.
I had the same when trying to
pip install lxml.
Edit: if you are installing as superuser (which will likely be the case if you are trying to append to
/Library/Python/2.7/site-packages, the native Apple factory-installed Python distribution which ships with OS X, rather than to some other Python distribution which you have subsequently installed yourself), then you will need to do, as described by @Thijs Kuipers in comments below:
sudo -E pip install psycopg2
or the equivalent, for whatever other package name you may be substituting in place of
UPDATE [2014-05-16]: Apple has fixed this problem with updated system Pythons (2.7, 2.6, and 2.5) in
OS X 10.9.3 so the workaround is no longer necessary when using the latest Mavericks and
Xcode 5.1+. However, as of now, the workaround is still required for
OS X 10.8.x (Mountain Lion, currently 10.8.5) if you are using
Xcode 5.1+ there.
Update: 10.9.3 resolves the issue with system CPython.
This is caused by the latest clang update from Apple that came with Xcode 5.1 today and is affecting many, many people, so hopefully a fix will appear soon.
Update: Did not expect this to get so much attention, but here's more detail: the clang 3.4 Apple is shipping defaults to erroring on unknown flags, but CPython builds modules using the same set of flags it was compiled with originally. The system CPython was compiled with several flags that are unknown by clang, thus causing this problem. The following are the current Mavericks (10.9.2) CPython compile flags:
-I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -fno-strict-aliasing -fno-common -dynamic -arch x86_64 -arch i386 -g -Os -pipe -fno-common -fno-strict-aliasing -fwrapv -mno-fused-madd -DENABLE_DTRACE -DMACOSX -DNDEBUG -Wall -Wstrict-prototypes -Wshorten-64-to-32 -DNDEBUG -g -fwrapv -Os -Wall -Wstrict-prototypes -DENABLE_DTRACE
To resolve this issue you have a few options:
ARCHFLAGS=-Wno-error=unused-command-line-argument-hard-error-in-futureto your compile flags.
- Strip the unsupported flags from the sysconfigdata.py (as is noted in another answer).
- Compile a new python using homebrew.
- Wait for the next OS X update, which is rumored to include recompiled Python/Ruby to remove this issue for system runtimes.