all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Aljosha Papsch <lists@rpapsch.de>
Cc: 21720@debbugs.gnu.org
Subject: bug#21720: Building gcc fails at target s-attrtab
Date: Sat, 24 Oct 2015 23:35:54 +0300	[thread overview]
Message-ID: <20151024233554.244e404b@debian-netbook> (raw)
In-Reply-To: <562A9EE4.3090702@rpapsch.de>

[-- Attachment #1: Type: text/plain, Size: 1890 bytes --]

On Fri, 23 Oct 2015 22:56:04 +0200
Aljosha Papsch <lists@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@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

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-10-24 20:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-20 17:22 bug#21720: Building gcc fails at target s-attrtab Aljosha Papsch
2015-10-21 16:38 ` Ludovic Courtès
2015-10-21 16:59   ` Andreas Enge
2015-10-21 23:12     ` Ludovic Courtès
2015-10-22 23:04   ` Aljosha Papsch
2015-10-23 20:56     ` Aljosha Papsch
2015-10-24 20:35       ` Efraim Flashner [this message]
2015-10-25 12:35         ` Aljosha Papsch
2015-10-25 13:25           ` Efraim Flashner
2015-10-25 21:06           ` Ludovic Courtès
2015-10-25 21:05     ` Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20151024233554.244e404b@debian-netbook \
    --to=efraim@flashner.co.il \
    --cc=21720@debbugs.gnu.org \
    --cc=lists@rpapsch.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.