[英]clang error: unknown argument: '-mno-fused-madd' (python package installation failure)
I get the following error when attempting to install psycopg2
via pip on Mavericks 10.9:尝试在 Mavericks 10.9 上通过 pip 安装psycopg2
时出现以下错误:
clang: error: unknown argument: '-mno-fused-madd' [-Wunused-command-line-argument-hard-error-in-future]
Not sure how to proceed and have searched here and elsewhere for this particular error.不确定如何继续,并已在此处和其他地方搜索此特定错误。 Any help is much appreciated!任何帮助深表感谢!
Here is the complete output from pip:这是 pip 的完整输出:
$ pip install psycopg2
Downloading/unpacking psycopg2
Downloading psycopg2-2.5.2.tar.gz (685kB): 685kB downloaded
Running setup.py (path:/private/var/folders/0z/ljjwsjmn4v9_zwm81vhxj69m0000gn/T/pip_build_tino/psycopg2/setup.py) egg_info for package psycopg2
Installing collected packages: psycopg2
Running setup.py install for psycopg2
building 'psycopg2._psycopg' extension
cc -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 -arch x86_64 -arch i386 -pipe -DPSYCOPG_DEFAULT_PYDATETIME=1 -DPSYCOPG_VERSION="2.5.2 (dt dec pq3 ext)" -DPG_VERSION_HEX=0x090303 -DPSYCOPG_EXTENSIONS=1 -DPSYCOPG_NEW_BOOLEAN=1 -DHAVE_PQFREEMEM=1 -I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -I. -I/usr/local/Cellar/postgresql/9.3.3/include -I/usr/local/Cellar/postgresql/9.3.3/include/server -c psycopg/psycopgmodule.c -o build/temp.macosx-10.9-intel-2.7/psycopg/psycopgmodule.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
Complete output from command /usr/bin/python -c "import setuptools, tokenize;__file__='/private/var/folders/0z/ljjwsjmn4v9_zwm81vhxj69m0000gn/T/pip_build_tino/psycopg2/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /var/folders/0z/ljjwsjmn4v9_zwm81vhxj69m0000gn/T/pip-bnWiwB-record/install-record.txt --single-version-externally-managed --compile:
running install
running build
running build_py
creating build
creating build/lib.macosx-10.9-intel-2.7
creating build/lib.macosx-10.9-intel-2.7/psycopg2
copying lib/__init__.py -> build/lib.macosx-10.9-intel-2.7/psycopg2
copying lib/_json.py -> build/lib.macosx-10.9-intel-2.7/psycopg2
copying lib/_range.py -> build/lib.macosx-10.9-intel-2.7/psycopg2
copying lib/errorcodes.py -> build/lib.macosx-10.9-intel-2.7/psycopg2
copying lib/extensions.py -> build/lib.macosx-10.9-intel-2.7/psycopg2
copying lib/extras.py -> build/lib.macosx-10.9-intel-2.7/psycopg2
copying lib/pool.py -> build/lib.macosx-10.9-intel-2.7/psycopg2
copying lib/psycopg1.py -> build/lib.macosx-10.9-intel-2.7/psycopg2
copying lib/tz.py -> build/lib.macosx-10.9-intel-2.7/psycopg2
creating build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/__init__.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/dbapi20.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/dbapi20_tpc.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_async.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_bug_gc.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_bugX000.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_cancel.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_connection.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_copy.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_cursor.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_dates.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_extras_dictcursor.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_green.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_lobject.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_module.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_notify.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_psycopg2_dbapi20.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_quote.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_transaction.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_types_basic.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_types_extras.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/test_with.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/testconfig.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
copying tests/testutils.py -> build/lib.macosx-10.9-intel-2.7/psycopg2/tests
running build_ext
building 'psycopg2._psycopg' extension
creating build/temp.macosx-10.9-intel-2.7
creating build/temp.macosx-10.9-intel-2.7/psycopg
cc -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 -arch x86_64 -arch i386 -pipe -DPSYCOPG_DEFAULT_PYDATETIME=1 -DPSYCOPG_VERSION="2.5.2 (dt dec pq3 ext)" -DPG_VERSION_HEX=0x090303 -DPSYCOPG_EXTENSIONS=1 -DPSYCOPG_NEW_BOOLEAN=1 -DHAVE_PQFREEMEM=1 -I/System/Library/Frameworks/Python.framework/Versions/2.7/include/python2.7 -I. -I/usr/local/Cellar/postgresql/9.3.3/include -I/usr/local/Cellar/postgresql/9.3.3/include/server -c psycopg/psycopgmodule.c -o build/temp.macosx-10.9-intel-2.7/psycopg/psycopgmodule.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
----------------------------------------
Cleaning up...
Command /usr/bin/python -c "import setuptools, tokenize;__file__='/private/var/folders/0z/ljjwsjmn4v9_zwm81vhxj69m0000gn/T/pip_build_tino/psycopg2/setup.py';exec(compile(getattr(tokenize, 'open', open)(__file__).read().replace('\r\n', '\n'), __file__, 'exec'))" install --record /var/folders/0z/ljjwsjmn4v9_zwm81vhxj69m0000gn/T/pip-bnWiwB-record/install-record.txt --single-version-externally-managed --compile failed with error code 1 in /private/var/folders/0z/ljjwsjmn4v9_zwm81vhxj69m0000gn/T/pip_build_tino/psycopg2
You can tell clang to not raise this as an error by setting the following environment variables prior compilation:您可以通过在编译之前设置以下环境变量来告诉 clang 不要将此作为错误引发:
export CFLAGS=-Qunused-arguments
export CPPFLAGS=-Qunused-arguments
Then pip install psycopg2
should work.然后pip install psycopg2
应该可以工作。
I had the same when trying to pip install lxml
.尝试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:编辑:如果您以超级用户身份安装(如果您尝试附加到/Library/Python/2.7/site-packages
,则可能是这种情况,即 OS X 附带的原生 Apple 工厂安装的 Python 发行版,而不是附加到您随后自己安装了一些其他 Python 发行版),那么您将需要这样做,如@Thijs Kuipers 在下面的评论中所述:
sudo -E pip install psycopg2
or the equivalent, for whatever other package name you may be substituting in place of psycopg2
.或等效的,对于您可能替换为psycopg2
任何其他包名称。
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+
.更新 [2014-05-16]:Apple 已在OS X 10.9.3
使用更新的系统 Python( Xcode 5.1+
和 2.5)修复了此问题,因此在使用最新的 Mavericks 和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.但是,到目前为止,如果您在那里使用Xcode 5.1+
, OS X 10.8.x
(Mountain Lion,目前为 10.8.5)仍然需要解决方法。
Update: 10.9.3 resolves the issue with system CPython.更新:10.9.3 解决了系统 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.这是由今天 Xcode 5.1 附带的 Apple 最新的 clang 更新引起的,并且影响了很多很多人,因此希望很快就会出现修复程序。
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.更新:没想到这会引起如此多的关注,但这里有更多细节:clang 3.4 Apple 正在发布默认为在未知标志上出错,但 CPython 使用与最初编译时使用的相同标志集构建模块。 The system CPython was compiled with several flags that are unknown by clang, thus causing this problem.系统CPython编译了几个clang未知的标志,从而导致了这个问题。 The following are the current Mavericks (10.9.2) CPython compile flags:以下是当前的 Mavericks (10.9.2) CPython 编译标志:
-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-future
to your compile flags.将ARCHFLAGS=-Wno-error=unused-command-line-argument-hard-error-in-future
到您的编译标志中。CFLAGS=""
通过CFLAGS=""
代码 5.1
ARCHFLAGS=-Wno-error=unused-command-line-argument-hard-error-in-future pip install psycopg2
Here is a work around that involves removing the flag from the python installation.这是一个解决方法,涉及从 python 安装中删除标志。
In /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/_sysconfigdata.py
are several places where the -mfused-madd
/ -mno-fused-madd
flag is set.在/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/_sysconfigdata.py
有几个设置-mfused-madd
/ -mno-fused-madd
标志的地方。
Edit this file and remove all of the references to that flag your compilation should work:编辑此文件并删除对该标志的所有引用,您的编译应该可以工作:
sudo sed -i '.old' 's/ -m\(no-\)\{0,1\}fused-madd //g' /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/_sysconfigdata.py
You need to delete the corresponding _sysconfigdata.pyc
and _sysconfigdata.pyo
files as well - at least on my system these files did not automatically get rebuilt:您还需要删除相应的_sysconfigdata.pyc
和_sysconfigdata.pyo
文件 - 至少在我的系统上,这些文件没有自动重建:
cd /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/
sudo rm _sysconfigdata.pyo _sysconfigdata.pyc
Note that have to use root access to make those changes.请注意,必须使用 root 访问权限才能进行这些更改。
I also edited the system python's notion of its original compile flags (as @user3405479 did).我还编辑了系统 python 对其原始编译标志的概念(如@user3405479 所做的那样)。 Instead of an editor I used command line tools to edit the file "in place" (the inode does change).我没有使用编辑器,而是使用命令行工具“就地”编辑文件(inode 确实发生了变化)。 I also compiled new pyo and pyc files instead of leaving them deleted.我还编译了新的 pyo 和 pyc 文件,而不是将它们删除。
The following commands are run as root, for example under sudo -i
以下命令以 root 身份运行,例如在sudo -i
pushd /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7
sed 's/-mno-fused-madd//g' _sysconfigdata.py \\ | diff -p _sysconfigdata.py - | patch -b
python -m py_compile _sysconfigdata.py
python -OO -m py_compile _sysconfigdata.py
popd
I used homebrew to install postgresql, and then wanted to install psycopg2 into the system-provided python 2.7 on Mavericks.我用homebrew安装了postgresql,然后想把psycopg2安装到系统自带的python 2.7上小牛。 To get that to work I ended up running this:为了让它工作,我最终运行了这个:
sudo ARCHFLAGS="-arch x86_64" CFLAGS=-Wunused-command-line-argument-hard-error-in-future pip install psycopg2
At least Apple is aware of this as this issue is discussed in the Xcode 5.1 Release Notes (Compiler section).至少 Apple 意识到了这一点,因为在 Xcode 5.1 发行说明(编译器部分)中讨论了这个问题。 Expect an updated Python and Ruby in the next OS update (fingers crossed!).期待在下一次操作系统更新中更新 Python 和 Ruby(手指交叉!)。 Also take note that the -Wno-error=unused-command-line-argument-hard-error-in-future
flag is meant to be a temporary workaround and will go away in the future (hopefully after system Python is fixed!).另请注意, -Wno-error=unused-command-line-argument-hard-error-in-future
标志是一种临时解决方法,将来会消失(希望在系统 Python 修复后!)。
If you are a Python package maintainer like me and want to save your users the hassle of working around this themselves, here is a solution (besides providing binary wheels/eggs) that goes into your setup.py
file:如果您是像我一样的 Python 包维护者,并希望为您的用户省去自己解决这个问题的麻烦,这里有一个解决方案(除了提供二进制轮子/鸡蛋),它会进入您的setup.py
文件:
from distutils.command.build_ext import build_ext
import subprocess
import sys
# Workaround for OS X 10.9.2 and Xcode 5.1+
# The latest clang treats unrecognized command-line options as errors and the
# Python CFLAGS variable contains unrecognized ones (e.g. -mno-fused-madd).
# See Xcode 5.1 Release Notes (Compiler section) and
# http://stackoverflow.com/questions/22313407 for more details. This workaround
# follows the approach suggested in http://stackoverflow.com/questions/724664.
class build_ext_subclass(build_ext):
def build_extensions(self):
if sys.platform == 'darwin':
# Test the compiler that will actually be used to see if it likes flags
proc = subprocess.Popen(self.compiler.compiler + ['-v'],
stdout=subprocess.PIPE, stderr=subprocess.PIPE,
universal_newlines=True)
stdout, stderr = proc.communicate()
clang_mesg = "clang: error: unknown argument: '-mno-fused-madd'"
if proc.returncode and stderr.splitlines()[0].startswith(clang_mesg):
for ext in self.extensions:
# Use temporary workaround to ignore invalid compiler option
# Hopefully -mno-fused-madd goes away before this workaround!
ext.extra_compile_args += ['-Wno-error=unused-command-line-argument-hard-error-in-future']
build_ext.build_extensions(self)
setup(
name="mypackage",
...
cmdclass={'build_ext' : build_ext_subclass},
...
)
None of the above solutions worked for me.以上解决方案都不适合我。 My situation is slightly different.我的情况略有不同。 I was trying to install rdiff-backup via homebrew when I got this error message.当我收到此错误消息时,我试图通过自制软件安装 rdiff-backup。
I apparently have both Apple's default python (2.7.5 @ /usr/bin/python) and Homebrew's python (2.7.6 @ /usr/local/Cellar/python/2.7.6/bin/python), but the error was coming from Apple's python.我显然有 Apple 的默认 python (2.7.5 @ /usr/bin/python) 和 Homebrew 的 python (2.7.6 @ /usr/local/Cellar/python/2.7.6/bin/python),但错误来了来自苹果的蟒蛇。
To fix the problem, basically I switched the python binaries.为了解决这个问题,基本上我切换了 python 二进制文件。
I did this via sudo:我是通过 sudo 做到的:
Then, 'brew install rdiff-backup' succeeded without any errors.然后,'brew install rdiff-backup' 成功而没有任何错误。
Finally, I did "mv /usr/bin/python_orig /usr/bin/python" to revert everything back.最后,我做了“mv /usr/bin/python_orig /usr/bin/python”来恢复一切。
You're probably on Python 2.7.5您可能使用的是 Python 2.7.5
$ python
Python 2.7.5 (default, Aug 25 2013, 00:04:04) [GCC 4.2.1 Compatible
Apple LLVM 5.0 (clang-500.0.68)] on darwin
Easiest solution go to www.python.org and install Python 2.7.6 which is compatible with the LLVM 5.1.最简单的解决方案是访问 www.python.org 并安装与 LLVM 5.1 兼容的 Python 2.7.6。
Then toast your old virtual environment, rmvirtualenv {virtual_env_name}
.然后敬酒您的旧虚拟环境rmvirtualenv {virtual_env_name}
。
Then make a new virtual env..然后创建一个新的虚拟环境..
mkvirtualenv --no-site-packages -p/Library/Frameworks/Python.framework/Versions/2.7/bin/python {virtual_env_name}
pip should work fine after this.在此之后 pip 应该可以正常工作。
Trying to pip install paramiko
on Amazon Linux AMI release 2016.09
gave me an error that included a link to this SO post.尝试在Amazon Linux AMI release 2016.09
pip install paramiko
上pip install paramiko
给了我一个错误,其中包含指向此 SO 帖子的链接。 So, even though it doesn't fit the OP's Title, I'm going to share the answer.因此,即使它不符合 OP 的标题,我还是要分享答案。
yum install libffi-devel
yum install gcc
yum install openssl-devel
pip install paramiko
Variation on the _sysconfigdata.py fix: use a virtual environment _sysconfigdata.py 修复的变化:使用虚拟环境
cp /System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/_sysconfigdata.py ${VIRTUAL_ENV}/lib/python2.7/_sysconfigdata.py
Then edit your copy at ${VIRTUAL_ENV}/lib/python2.7/_sysconfigdata.py然后在 ${VIRTUAL_ENV}/lib/python2.7/_sysconfigdata.py 编辑您的副本
I removed all the occurences of '-mno-fused-madd' and then builds worked in that virtualenv.我删除了'-mno-fused-madd'的所有出现,然后在那个virtualenv中构建工作。
No root needed!无需root!
For me, the bad flags were explicitly given in the package's Makefile.对我来说,包的 Makefile 中明确给出了坏标志。 So I had to edit the makefile to remove the unrecognized flag from the erroring package.所以我不得不编辑 makefile 以从错误包中删除无法识别的标志。
Upgrading Homebrew and installing unixodbc solved it for me升级 Homebrew 并安装 unixodbc 为我解决了这个问题
brew upgrade
brew install unixodbc
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.