GNU bug report logs - #21720
Building gcc fails at target s-attrtab

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 21720 in the body.
You can then email your comments to 21720 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Aljosha Papsch <lists <at> rpapsch.de>
To: bug-guix <at> gnu.org
Subject: Building gcc fails at target s-attrtab
Date: Tue, 20 Oct 2015 19:22:09 +0200

[Message part 1 (text/plain, inline)]

Hello,

I installed Guix 0.8.3 on an Arch machine and tried to install zile, 
because it has few dependencies. Though some files are downloaded from 
hydra.gnu.org, guix tries to build packages. It fails at gcc's build at 
target s-attrtab. When doing "guix pull", building also fails at 
gcc-cross-boot0's target s-attrtab.

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.

Best regards,
Aljosha Papsch

[0] https://lists.gnu.org/archive/html/guix-devel/2014-11/msg00427.html

[Message part 2 (text/html, inline)]

[w0ym9mxwwmkf9m70mkldmybbryf454-gcc-cross-boot0-4.9.3.drv (text/plain, attachment)]

Message #8 received at 21720 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Aljosha Papsch <lists <at> rpapsch.de>
Cc: 21720 <at> debbugs.gnu.org
Subject: Re: bug#21720: Building gcc fails at target s-attrtab
Date: Wed, 21 Oct 2015 18:38:17 +0200

Aljosha Papsch <lists <at> rpapsch.de> skribis:

> I installed Guix 0.8.3 on an Arch machine and tried to install zile,
> because it has few dependencies. Though some files are downloaded from
> hydra.gnu.org, guix tries to build packages.

Sounds like binaries for 0.8.3 have been GC’d from hydra.gnu.org, which
is unfortunate.

> It fails at gcc's build at target s-attrtab. When doing "guix pull",
> building also fails at gcc-cross-boot0's target s-attrtab.

Hmm, OK.

> 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?

> 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?

Thanks for your report!

Ludo’.

Message #11 received at 21720 <at> debbugs.gnu.org (full text, mbox):

From: Andreas Enge <andreas <at> enge.fr>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 21720 <at> debbugs.gnu.org, Aljosha Papsch <lists <at> rpapsch.de>
Subject: Re: bug#21720: Building gcc fails at target s-attrtab
Date: Wed, 21 Oct 2015 18:59:12 +0200

On Wed, Oct 21, 2015 at 06:38:17PM +0200, Ludovic Courtès wrote:
> Sounds like binaries for 0.8.3 have been GC’d from hydra.gnu.org, which
> is unfortunate.

Maybe after each release, we should create a profile with all the packages
of this release (and delete it again after the next release)? Or are we
too low on disk space?

Andreas

Message #14 received at 21720 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas <at> enge.fr>
Cc: 21720 <at> debbugs.gnu.org, Aljosha Papsch <lists <at> rpapsch.de>
Subject: Re: bug#21720: Building gcc fails at target s-attrtab
Date: Thu, 22 Oct 2015 01:12:18 +0200

Andreas Enge <andreas <at> enge.fr> skribis:

> On Wed, Oct 21, 2015 at 06:38:17PM +0200, Ludovic Courtès wrote:
>> Sounds like binaries for 0.8.3 have been GC’d from hydra.gnu.org, which
>> is unfortunate.
>
> Maybe after each release, we should create a profile with all the packages
> of this release (and delete it again after the next release)?

That was the plan, hence the ‘version-0.8.3’ branch but…

> Or are we too low on disk space?

… probably.

Ludo’.

Message #17 received at 21720 <at> debbugs.gnu.org (full text, mbox):

From: Aljosha Papsch <lists <at> rpapsch.de>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 21720 <at> debbugs.gnu.org
Subject: Re: bug#21720: Building gcc fails at target s-attrtab
Date: Fri, 23 Oct 2015 01:04:05 +0200

[Message part 1 (text/plain, inline)]

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.

Aljosha

[2kj5a59dymn0dhg0v09xqhc4hsxgsv-gcc-4.9.3.drv (text/plain, attachment)]

[dmesg.log (text/x-log, attachment)]

Message #20 received at 21720 <at> debbugs.gnu.org (full text, mbox):

From: Aljosha Papsch <lists <at> rpapsch.de>
To: Ludovic Courtès <ludo <at> gnu.org>
Cc: 21720 <at> debbugs.gnu.org
Subject: Re: bug#21720: Building gcc fails at target s-attrtab
Date: Fri, 23 Oct 2015 22:56:04 +0200

[Message part 1 (text/plain, inline)]

On 23.10.2015 01:04, Aljosha Papsch wrote:
> 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 hooked up an old 4GB swap partition and during the build process it 
was used a bit. This time, the build process got a little further, but 
it got stuck again at another phase. Please see the attached build log. 
The error message is "No space left on device", though the file system 
on wich guix runs has 85GB left.

Dmesg isn't helpful this time, an error should appear between these two 
messages:
[17910.001324] Adding 3948540k swap on /dev/mapper/fed-swap. Priority:-1 
extents:1 across:3948540k FS
[18118.026198] wlp0s26u1u2: AP 00:00:00:00:00:00 changed bandwidth, new 
config is 2412 MHz, width 1 (2412/0 MHz)

For the fun of it, I plotted the memory consumption using gnuplot. While 
the build process was busy, I captured memory usage with "free -s1 > 
memory.log". A little scheme helped transform that into a data file for 
gnuplot. The x axis is the datum, e.g. nth capture. Near the end, free 
memory goes up sharply. This is where the build process failed and the 
machine went idle.

Aljosha

[6pakkby1qg17ssj4k9nrhh9iswii49-gcc-4.9.3.drv (text/plain, attachment)]

[swap-plot.png (image/png, attachment)]

[memory-plot.png (image/png, attachment)]

Message #23 received at 21720 <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: Aljosha Papsch <lists <at> rpapsch.de>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 21720 <at> debbugs.gnu.org
Subject: Re: bug#21720: Building gcc fails at target s-attrtab
Date: Sat, 24 Oct 2015 23:35:54 +0300

[Message part 1 (text/plain, inline)]

On Fri, 23 Oct 2015 22:56:04 +0200
Aljosha Papsch <lists <at> rpapsch.de> wrote:

> On 23.10.2015 01:04, Aljosha Papsch wrote:
> > 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 hooked up an old 4GB swap partition and during the build process it 
> was used a bit. This time, the build process got a little further, but 
> it got stuck again at another phase. Please see the attached build log. 
> The error message is "No space left on device", though the file system 
> on wich guix runs has 85GB left.

the error message is near the end of the log:
../../gcc-4.9.3/gcc/tree-ssa-ccp.c:2751:1: fatal error: error writing to /tmp/nix-build-gcc-4.9.3.drv-0/cc5mntgw.s: No space left on device
 }
I assume /tmp is part of / on your system. How much free space do you have
there? That's where the building is done.

> 
> Dmesg isn't helpful this time, an error should appear between these two 
> messages:
> [17910.001324] Adding 3948540k swap on /dev/mapper/fed-swap. Priority:-1 
> extents:1 across:3948540k FS
> [18118.026198] wlp0s26u1u2: AP 00:00:00:00:00:00 changed bandwidth, new 
> config is 2412 MHz, width 1 (2412/0 MHz)
> 
> For the fun of it, I plotted the memory consumption using gnuplot. While 
> the build process was busy, I captured memory usage with "free -s1 > 
> memory.log". A little scheme helped transform that into a data file for 
> gnuplot. The x axis is the datum, e.g. nth capture. Near the end, free 
> memory goes up sharply. This is where the build process failed and the 
> machine went idle.
> 
> Aljosha



-- 
Efraim Flashner   <efraim <at> flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[Message part 2 (application/pgp-signature, inline)]

Message #26 received at 21720 <at> debbugs.gnu.org (full text, mbox):

From: Efraim Flashner <efraim <at> flashner.co.il>
To: Aljosha Papsch <lists <at> rpapsch.de>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 21720 <at> debbugs.gnu.org
Subject: Re: bug#21720: Building gcc fails at target s-attrtab
Date: Sun, 25 Oct 2015 15:25:23 +0200

[Message part 1 (text/plain, inline)]

On Sun, 25 Oct 2015 13:35:22 +0100
Aljosha Papsch <lists <at> rpapsch.de> wrote:

> On 24.10.2015 22:35, Efraim Flashner wrote:
> > the error message is near the end of the log: 
> > ../../gcc-4.9.3/gcc/tree-ssa-ccp.c:2751:1: fatal error: error writing 
> > to /tmp/nix-build-gcc-4.9.3.drv-0/cc5mntgw.s: No space left on device 
> > } I assume /tmp is part of / on your system. How much free space do 
> > you have there? That's where the building is done.   
> 
> That was the nudge in the right direction. I didn't think of /tmp being 
> mounted as tmpfs, which lead to wrong assumption that guix had 85GB 
> space left. /tmp is mounted with default options, which means size is 
> half the RAM (2GB). To increase tmpfs size, I remounted /tmp with 
> options "size=20G". These 20GB are backed by 50GB swap, which I 
> increased by reusing an old partition of another system as swap.
> 
> Now building zile suceeds and guix installed it successfully. I guess 
> the bug can be closed now as it appears to be a sole issue of memory 
> resources on this machine. Utilizing gnuplot again, the peak of RAM 
> usage is at approx. 1.8GB, while swap usage is at approx. 1.3GB. The 
> 20GB tmpfs and 50GB swap is a bit much and I'll reduce it to 3GB tmpfs 
> and 6GB swap. I will see if this is sufficient in daily guix usage.
> 
> Aljosha

Glad to hear it worked out :)

my /tmp is a 6GB tmpfs, because for a while I was building and building
texlive, and after whatever else was in /tmp it needed almost 5GB. But that
should be the biggest package.

-- 
Efraim Flashner   <efraim <at> flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[Message part 2 (application/pgp-signature, inline)]

Message #29 received at 21720 <at> debbugs.gnu.org (full text, mbox):

From: Aljosha Papsch <lists <at> rpapsch.de>
To: Efraim Flashner <efraim <at> flashner.co.il>
Cc: Ludovic Courtès <ludo <at> gnu.org>, 21720 <at> debbugs.gnu.org
Subject: Re: bug#21720: Building gcc fails at target s-attrtab
Date: Sun, 25 Oct 2015 13:35:22 +0100

On 24.10.2015 22:35, Efraim Flashner wrote:
> the error message is near the end of the log: 
> ../../gcc-4.9.3/gcc/tree-ssa-ccp.c:2751:1: fatal error: error writing 
> to /tmp/nix-build-gcc-4.9.3.drv-0/cc5mntgw.s: No space left on device 
> } I assume /tmp is part of / on your system. How much free space do 
> you have there? That's where the building is done. 

That was the nudge in the right direction. I didn't think of /tmp being 
mounted as tmpfs, which lead to wrong assumption that guix had 85GB 
space left. /tmp is mounted with default options, which means size is 
half the RAM (2GB). To increase tmpfs size, I remounted /tmp with 
options "size=20G". These 20GB are backed by 50GB swap, which I 
increased by reusing an old partition of another system as swap.

Now building zile suceeds and guix installed it successfully. I guess 
the bug can be closed now as it appears to be a sole issue of memory 
resources on this machine. Utilizing gnuplot again, the peak of RAM 
usage is at approx. 1.8GB, while swap usage is at approx. 1.3GB. The 
20GB tmpfs and 50GB swap is a bit much and I'll reduce it to 3GB tmpfs 
and 6GB swap. I will see if this is sufficient in daily guix usage.

Aljosha

Message #32 received at 21720 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Aljosha Papsch <lists <at> rpapsch.de>
Cc: 21720 <at> debbugs.gnu.org
Subject: Re: bug#21720: Building gcc fails at target s-attrtab
Date: Sun, 25 Oct 2015 22:05:07 +0100

Aljosha Papsch <lists <at> rpapsch.de> skribis:

> On 21.10.2015 18:38, Ludovic Courtès wrote:

[...]

>> 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.

I regularly build it on my laptop, which has 8G of RAM and little swap.
The build machines behind hydra.gnu.org all have more than 4G of RAM, I
think.

> [ 2779.152334] genattrtab invoked oom-killer: gfp_mask=0x280da, order=0, oom_score_adj=0

Indeed, ‘genattrtab’ is a program in GCC used when building it.  It’s a
problem that it needs so much memory.  I would suggest reporting it if
nobody did that already.

Thanks,
Ludo’.

Message #35 received at 21720 <at> debbugs.gnu.org (full text, mbox):

From: ludo <at> gnu.org (Ludovic Courtès)
To: Aljosha Papsch <lists <at> rpapsch.de>
Cc: 21720 <at> debbugs.gnu.org, Efraim Flashner <efraim <at> flashner.co.il>
Subject: Re: bug#21720: Building gcc fails at target s-attrtab
Date: Sun, 25 Oct 2015 22:06:49 +0100

Aljosha Papsch <lists <at> rpapsch.de> skribis:

> On 24.10.2015 22:35, Efraim Flashner wrote:
>> the error message is near the end of the log:
>> ../../gcc-4.9.3/gcc/tree-ssa-ccp.c:2751:1: fatal error: error
>> writing to /tmp/nix-build-gcc-4.9.3.drv-0/cc5mntgw.s: No space left
>> on device } I assume /tmp is part of / on your system. How much free
>> space do you have there? That's where the building is done. 
>
> That was the nudge in the right direction. I didn't think of /tmp
> being mounted as tmpfs,

Ooh, that also explains the out-of-memory issue, then.

Well, thanks for finding it out!

Closing this bug now.

Ludo’.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.