Linux g++ 4.6.1 编译器错误：错误：未知伪操作：`.cfi_personality'

g++ 4.6.1 compiler error: Error: unknown pseudo-op: `.cfi_personality'

提问by daj

I have a file which compiles without errors or warnings on my macbook pro running osx (snow leopard) using g++ (4.6.1). I just uploaded it to our linux cluster (not run by me) and tried to compile there (also using gcc 4.6.1). This time I many strange error messages with the assembler. How do I interpret the following error?

我有一个使用 g++ (4.6.1) 在运行 osx (snow leopard) 的 macbook pro 上编译时没有错误或警告的文件。我刚刚将它上传到我们的 linux 集群（不是由我运行）并尝试在那里编译（也使用 gcc 4.6.1）。这次我用汇编器出现了很多奇怪的错误信息。我如何解释以下错误？

g++ -I../shared/boost_1_47_0 -std=c++0x -O2  -c ../shared/ft.cpp -o ../shared/ft.o

/tmp/ccEqihNa.s: Assembler messages:
/tmp/ccEqihNa.s:809: Error: unknown pseudo-op: `.cfi_personality'
/tmp/ccEqihNa.s:810: Error: unknown pseudo-op: `.cfi_lsda'
/tmp/ccEqihNa.s:1055: Error: unknown pseudo-op: `.cfi_personality'
/tmp/ccEqihNa.s:1056: Error: unknown pseudo-op: `.cfi_lsda'
:145: Error: unknown pseudo-op: `.cfi_personality'
:146: Error: unknown pseudo-op: `.cfi_lsda'
:248: Error: unknown pseudo-op: `.cfi_personality'
:249: Error: unknown pseudo-op: `.cfi_lsda'
:351: Error: unknown pseudo-op: `.cfi_personality'
:352: Error: unknown pseudo-op: `.cfi_lsda'
:496: Error: unknown pseudo-op: `.cfi_personality'
:497: Error: unknown pseudo-op: `.cfi_lsda'
:988: Error: unknown pseudo-op: `.cfi_personality'
:989: Error: unknown pseudo-op: `.cfi_lsda'
:1488: Error: unknown pseudo-op: `.cfi_personality'
:1489: Error: unknown pseudo-op: `.cfi_lsda'
:2333: Error: unknown pseudo-op: `.cfi_personality'
:2334: Error: unknown pseudo-op: `.cfi_lsda'
:2460: Error: unknown pseudo-op: `.cfi_personality'
:2461: Error: unknown pseudo-op: `.cfi_lsda'
:2899: Error: unknown pseudo-op: `.cfi_personality'
:2900: Error: unknown pseudo-op: `.cfi_lsda'
:3053: Error: unknown pseudo-op: `.cfi_personality'
:3054: Error: unknown pseudo-op: `.cfi_lsda'
:3144: Error: unknown pseudo-op: `.cfi_personality'
:3145: Error: unknown pseudo-op: `.cfi_lsda'
:3205: Error: unknown pseudo-op: `.cfi_personality'
:3206: Error: unknown pseudo-op: `.cfi_lsda'
:3296: Error: unknown pseudo-op: `.cfi_personality'
:3297: Error: unknown pseudo-op: `.cfi_lsda'
:4090: Error: unknown pseudo-op: `.cfi_personality'
:4091: Error: unknown pseudo-op: `.cfi_lsda'
:4921: Error: unknown pseudo-op: `.cfi_personality'
:4922: Error: unknown pseudo-op: `.cfi_lsda'
:5094: Error: unknown pseudo-op: `.cfi_personality'
:5095: Error: unknown pseudo-op: `.cfi_lsda'
:5274: Error: unknown pseudo-op: `.cfi_personality'
:5275: Error: unknown pseudo-op: `.cfi_lsda'
:5365: Error: unknown pseudo-op: `.cfi_personality'
:5366: Error: unknown pseudo-op: `.cfi_lsda'
:5426: Error: unknown pseudo-op: `.cfi_personality'
:5427: Error: unknown pseudo-op: `.cfi_lsda'
:5525: Error: unknown pseudo-op: `.cfi_personality'
:5526: Error: unknown pseudo-op: `.cfi_lsda'
:5744: Error: unknown pseudo-op: `.cfi_personality'
:5745: Error: unknown pseudo-op: `.cfi_lsda'
:5919: Error: unknown pseudo-op: `.cfi_personality'
:5920: Error: unknown pseudo-op: `.cfi_lsda'
:6097: Error: unknown pseudo-op: `.cfi_personality'
:6098: Error: unknown pseudo-op: `.cfi_lsda'
:6209: Error: unknown pseudo-op: `.cfi_personality'
:6210: Error: unknown pseudo-op: `.cfi_lsda'
:6305: Error: unknown pseudo-op: `.cfi_personality'
:6306: Error: unknown pseudo-op: `.cfi_lsda'
:6735: Error: unknown pseudo-op: `.cfi_personality'
:6736: Error: unknown pseudo-op: `.cfi_lsda'
:7082: Error: unknown pseudo-op: `.cfi_personality'
:7083: Error: unknown pseudo-op: `.cfi_lsda'
:7355: Error: unknown pseudo-op: `.cfi_personality'
:7356: Error: unknown pseudo-op: `.cfi_lsda'
:7663: Error: unknown pseudo-op: `.cfi_personality'
:7664: Error: unknown pseudo-op: `.cfi_lsda'
:8139: Error: unknown pseudo-op: `.cfi_personality'
:8140: Error: unknown pseudo-op: `.cfi_lsda'
:8605: Error: unknown pseudo-op: `.cfi_personality'
:8606: Error: unknown pseudo-op: `.cfi_lsda'
:8894: Error: unknown pseudo-op: `.cfi_personality'
:8895: Error: unknown pseudo-op: `.cfi_lsda'
:9224: Error: unknown pseudo-op: `.cfi_personality'
:9225: Error: unknown pseudo-op: `.cfi_lsda'
:9531: Error: unknown pseudo-op: `.cfi_personality'
:9532: Error: unknown pseudo-op: `.cfi_lsda'
:9868: Error: unknown pseudo-op: `.cfi_personality'
:9869: Error: unknown pseudo-op: `.cfi_lsda'
:10313: Error: unknown pseudo-op: `.cfi_personality'
:10314: Error: unknown pseudo-op: `.cfi_lsda'
:10533: Error: unknown pseudo-op: `.cfi_personality'
:10534: Error: unknown pseudo-op: `.cfi_lsda'
:11052: Error: unknown pseudo-op: `.cfi_personality'
:11053: Error: unknown pseudo-op: `.cfi_lsda'
:11324: Error: unknown pseudo-op: `.cfi_personality'
:11325: Error: unknown pseudo-op: `.cfi_lsda'
:13561: Error: unknown pseudo-op: `.cfi_personality'
:13562: Error: unknown pseudo-op: `.cfi_lsda'
:13941: Error: unknown pseudo-op: `.cfi_personality'
:13942: Error: unknown pseudo-op: `.cfi_lsda'
:14340: Error: unknown pseudo-op: `.cfi_personality'
:14341: Error: unknown pseudo-op: `.cfi_lsda'
:14711: Error: unknown pseudo-op: `.cfi_personality'
:14712: Error: unknown pseudo-op: `.cfi_lsda'
:14862: Error: unknown pseudo-op: `.cfi_personality'
:14863: Error: unknown pseudo-op: `.cfi_lsda'
:14963: Error: unknown pseudo-op: `.cfi_personality'
:14964: Error: unknown pseudo-op: `.cfi_lsda'
:15381: Error: unknown pseudo-op: `.cfi_personality'
:15382: Error: unknown pseudo-op: `.cfi_lsda'
:15792: Error: unknown pseudo-op: `.cfi_personality'
:15793: Error: unknown pseudo-op: `.cfi_lsda'
:16293: Error: unknown pseudo-op: `.cfi_personality'
:16294: Error: unknown pseudo-op: `.cfi_lsda'
:16445: Error: unknown pseudo-op: `.cfi_personality'
:16446: Error: unknown pseudo-op: `.cfi_lsda'
:17045: Error: unknown pseudo-op: `.cfi_personality'
:17046: Error: unknown pseudo-op: `.cfi_lsda'
:18020: Error: unknown pseudo-op: `.cfi_personality'
:18021: Error: unknown pseudo-op: `.cfi_lsda'
:18111: Error: unknown pseudo-op: `.cfi_personality'
:18112: Error: unknown pseudo-op: `.cfi_lsda'
:18172: Error: unknown pseudo-op: `.cfi_personality'
:18173: Error: unknown pseudo-op: `.cfi_lsda'
:139: Error: unknown pseudo-op: `.cfi_personality'
:140: Error: unknown pseudo-op: `.cfi_lsda'
:554: Error: unknown pseudo-op: `.cfi_personality'
:555: Error: unknown pseudo-op: `.cfi_lsda'
:654: Error: unknown pseudo-op: `.cfi_personality'
:655: Error: unknown pseudo-op: `.cfi_lsda'
:1344: Error: unknown pseudo-op: `.cfi_personality'
:1345: Error: unknown pseudo-op: `.cfi_lsda'
:1831: Error: unknown pseudo-op: `.cfi_personality'
:1832: Error: unknown pseudo-op: `.cfi_lsda'
:2522: Error: unknown pseudo-op: `.cfi_personality'
:2523: Error: unknown pseudo-op: `.cfi_lsda'
:3061: Error: unknown pseudo-op: `.cfi_personality'
:3062: Error: unknown pseudo-op: `.cfi_lsda'
:3284: Error: unknown pseudo-op: `.cfi_personality'
:3285: Error: unknown pseudo-op: `.cfi_lsda'
:3515: Error: unknown pseudo-op: `.cfi_personality'
:3516: Error: unknown pseudo-op: `.cfi_lsda'
:3745: Error: unknown pseudo-op: `.cfi_personality'
:3746: Error: unknown pseudo-op: `.cfi_lsda'
:3996: Error: unknown pseudo-op: `.cfi_personality'
:3997: Error: unknown pseudo-op: `.cfi_lsda'
:4518: Error: unknown pseudo-op: `.cfi_personality'
:4519: Error: unknown pseudo-op: `.cfi_lsda'
:5489: Error: unknown pseudo-op: `.cfi_personality'
:5490: Error: unknown pseudo-op: `.cfi_lsda'
:6382: Error: unknown pseudo-op: `.cfi_personality'
:6383: Error: unknown pseudo-op: `.cfi_lsda'
:6547: Error: unknown pseudo-op: `.cfi_personality'
:6548: Error: unknown pseudo-op: `.cfi_lsda'
:6651: Error: unknown pseudo-op: `.cfi_personality'
:6652: Error: unknown pseudo-op: `.cfi_lsda'
:6712: Error: unknown pseudo-op: `.cfi_personality'
:6713: Error: unknown pseudo-op: `.cfi_lsda'
:7146: Error: unknown pseudo-op: `.cfi_personality'
:7147: Error: unknown pseudo-op: `.cfi_lsda'
:7367: Error: unknown pseudo-op: `.cfi_personality'
:7368: Error: unknown pseudo-op: `.cfi_lsda'
:7597: Error: unknown pseudo-op: `.cfi_personality'
:7598: Error: unknown pseudo-op: `.cfi_lsda'
:9275: Error: unknown pseudo-op: `.cfi_personality'
:9276: Error: unknown pseudo-op: `.cfi_lsda'
:9562: Error: unknown pseudo-op: `.cfi_personality'
:9563: Error: unknown pseudo-op: `.cfi_lsda'
:10065: Error: unknown pseudo-op: `.cfi_personality'
:10066: Error: unknown pseudo-op: `.cfi_lsda'
:10326: Error: unknown pseudo-op: `.cfi_personality'
:10327: Error: unknown pseudo-op: `.cfi_lsda'
:10534: Error: unknown pseudo-op: `.cfi_personality'
:10535: Error: unknown pseudo-op: `.cfi_lsda'
:11978: Error: unknown pseudo-op: `.cfi_personality'
:11979: Error: unknown pseudo-op: `.cfi_lsda'
:12091: Error: unknown pseudo-op: `.cfi_personality'
:12092: Error: unknown pseudo-op: `.cfi_lsda'
:12936: Error: unknown pseudo-op: `.cfi_personality'
:12937: Error: unknown pseudo-op: `.cfi_lsda'
:14294: Error: unknown pseudo-op: `.cfi_personality'
:14295: Error: unknown pseudo-op: `.cfi_lsda'
:16088: Error: unknown pseudo-op: `.cfi_personality'
:16089: Error: unknown pseudo-op: `.cfi_lsda'

采纳答案by Employed Russian

The error means that your assembler (likely /usr/bin/as, part of binutils) is too old.

该错误意味着您的汇编程序（可能/usr/bin/as是 binutils 的一部分）太旧了。

The patch that added them appears to be this one. Unfortunately, the binutils NEWS file doesn't explicitly reference this addition, but since it was added in 2006, I expect any recent version of binutils would do.

添加它们的补丁似乎就是这个补丁。不幸的是，binutils NEWS 文件没有明确引用这个添加项，但由于它是在 2006 年添加的，我希望任何最新版本的 binutils 都可以。

回答by mike-v

I had this error pop up due to gcc and g++ pointing to different versions. For any that come across this error and have recently upgraded gcc/g++ check this:

由于 gcc 和 g++ 指向不同的版本，我弹出了这个错误。对于遇到此错误并且最近升级了 gcc/g++ 的任何人，请检查以下内容：

gcc --version

matches this:

匹配这个：

g++ --version

If not you will have to review the links via

如果不是，您将不得不通过以下方式查看链接

ls `which g++` -al

and

和

ls `which gcc` -al

回答by gemesyscanada

Very helpful this question. I ran into this assembler message compiling a large application, using gcc 4.4.7 on CentOS 6.6 (Final). Exact (or so I thought) environment was running on another box. Error was: "unknown pseudo-op: `.p2align$3' ". I checked versions of /usr/bin/gcc and /usr/bin/g++ and /usr/bin/as, and all seemed isometric between boxes. But on more careful inspection, the gcc on successful box was "4.4.7-18.el6.i686", and on the failing platform: "4.4.7-11.el6.i686". Seemed unlikely such a small version difference could matter - but it did. Since both boxes were CentOS, I was able to just "yum update gcc-4.7.7" on the box with the error, and this brought in 22mb of 9 different files, as it upgraded gcc and all its dependent libraries. (I didn't want to fully upgrade gcc, since the idea was to ensure exact alignment between platforms first. The "yum update ..." brought in all the 4.4.7-18 versions, just as it is supposed to do.) I needed to just re-run "make", and it took off from where the fail had occurred and the compile run to successfull completion.

这个问题很有帮助。我在 CentOS 6.6（最终版）上使用 gcc 4.4.7 编译一个大型应用程序时遇到了这个汇编器消息。确切的（或者我认为）环境正在另一个盒子上运行。错误是：“未知的伪操作：`.p2align$3'”。我检查了 /usr/bin/gcc 和 /usr/bin/g++ 和 /usr/bin/as 的版本，并且所有盒子之间似乎都是等距的。但仔细检查，成功的盒子上的 gcc 是“4.4.7-18.el6.i686”，而失败的平台上的 gcc 是“4.4.7-11.el6.i686”。如此小的版本差异似乎不太可能重要 - 但确实如此。由于两个盒子都是 CentOS，我只能在有错误的盒子上“yum update gcc-4.7.7”，这带来了 22mb 的 9 个不同文件，因为它升级了 gcc 及其所有依赖库。（我不想完全升级 gcc，因为这个想法是首先确保平台之间的精确对齐。“yum update ...”带来了所有 4.4.7-18 版本，正如它应该做的那样。）我需要重新运行“make”，它从发生故障的地方起飞，编译运行成功完成。