[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#21720: Building gcc fails at target s-attrtab

From: Aljosha Papsch
Subject: bug#21720: Building gcc fails at target s-attrtab
Date: Fri, 23 Oct 2015 01:04:05 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Icedove/38.3.0

On 21.10.2015 18:38, Ludovic Courtès wrote:
Looking around a bit, I found [0]. Apparently someone had the same
issue, though discussion broke off, because the reporter wasn't able
to provide the build log, so here it is for gcc-cross-boot0 (last 200
lines). Maybe we can just lift off where the previous discussion died.
Is this deterministic?  That is, does it happen again if you rerun ‘guix
build zile’ or something like that?
Yes, "guix build zile" fails again at GCCs build. I attached the build log just to be sure.
Makefile:2107: recipe for target 's-attrtab' failed
make[2]: *** [s-attrtab] Killed
The “Killed” here suggests an out-of-memory condition.  Does
‘dmesg | tail’ reveal something like that?

How much memory does this machine have?
It got 4GB of RAM but none of swap. dmesg really shows something, please see attachment. I'll try hooking up some swap and see how it goes.

I'm curious: How did you compile gcc in the past, where resources were even more scarce? Did you always have a good load of swap for it to succeed? I remember the rule "swap is 2 times ram", though in recent years some are convinced that it worn off given the ever bigger RAM.


Attachment: 2kj5a59dymn0dhg0v09xqhc4hsxgsv-gcc-4.9.3.drv
Description: Text document

Attachment: dmesg.log
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]