Gentoo GCC失败了 [英] Gentoo GCC failed emerge

查看:225
本文介绍了Gentoo GCC失败了的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在尝试恢复具有内核2.6.32的Gentoo Linux的旧安装,并且我可以更新@system,但有例外:gcc 4.5.4安装失败. 最后几行在这里:

i'm trying to resurrect an old installation of Gentoo Linux that has kernel 2.6.32 and i could update @system with an exception: gcc 4.5.4 failed installation. The last lines are here:

http://pastebin.com/8s4z0FJy

如果需要更多信息,请问我,我回家后会发布一些信息(通过SSH获取该信息). 甚至GHC都无法编译,但我稍后会处理.我需要GCC来编译其他软件包. 预先感谢

Ask me if you need more info, i'll post something more when i get home (Got that info through SSH). Even GHC fails compiling but i'll handle that later. I need GCC in order to compile the other packages. Thanks in advance

推荐答案

使用谷歌搜索响应另一个链接:

To respond to a link with another link from googling: https://forums.gentoo.org/viewtopic-t-896518-start-0.html. Let me summarize that thread:

{standard input}: Assembler messages:
{standard input}:87553: Warning: end of file not at end of a line; newline inserted
{standard input}:88534: Error: unknown pseudo-op: `.l38'
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
xgcc: Internal error: Killed (program cc1)

基本上,出现汇编错误是因为gcc的汇编输出在被杀死时被中断了. Gentoo论坛线程暗示,这可能是因为gcc占用了过多的内存.您可以通过检查dmesg输出的末尾OOM内容来确认这一点.如果不是内存问题,那么您可能有一个真正的错误,应遵循粘贴文本中的说明将错误报告给 https://bugs.gentoo.org/.但是,请先查看是否是内存问题.

Basically, the assembly errors come because gcc’s assembly output was interrupted when it was killed. The Gentoo forums thread suggests this may likely be because gcc used up too much memory. You can confirm this by checking near the end of dmesg’s output for OOM stuff. If memory is not the issue, then you might have a real bug and should follow the instructions in the text you pastebined for reporting the bug to https://bugs.gentoo.org/. But, please try seeing if memory is the issue first.

如果出现内存问题,请确保您的计算机上具有交换分区并已启用它们.您可以通过运行swapon -s查看启用的交换分区的摘要.如果没有任何显示,并且您无法重新分区,则可以始终使用# ( umask 0077 && dd if=/dev/zero of=/.swap.img bs=1M count=1024 && mkswap /.swap.img && swapon /.swap.img )之类的技巧(#"表示root shell提示符,因此请不要实际键入).论坛主题还建议从CFLAGSCXXFLAGS中删除-pipe(这会导致gcc使用更多的内存而不是写出大量的临时文件)(通过编辑/etc/make.conf/etc/portage/make.conf(以存在的任何一个为准)).我们无法从您发布的内容中分辨出您的CFLAGS是什么.

If memory is the issue, make sure that you have swap partitions on your machine and that they are enabled. You can view a summary of your enabled swap partitions by running swapon -s. If nothing shows up and you cannot repartition, you can always use a trick like # ( umask 0077 && dd if=/dev/zero of=/.swap.img bs=1M count=1024 && mkswap /.swap.img && swapon /.swap.img ) (the ‘#’ indicates a root shell prompt, so don’t actually type it). The forum thread also suggests that removing -pipe, which causes gcc to use more memory instead of writing out lots of temporary files, from CFLAGS and CXXFLAGS (by editing /etc/make.conf or /etc/portage/make.conf, whichever exists). We cannot tell what your CFLAGS are from what you posted.

这篇关于Gentoo GCC失败了的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆