From: Aljosha Papsch <lists@rpapsch.de>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: 21720@debbugs.gnu.org
Subject: bug#21720: Building gcc fails at target s-attrtab
Date: Sun, 25 Oct 2015 13:35:22 +0100 [thread overview]
Message-ID: <562CCC8A.80407@rpapsch.de> (raw)
In-Reply-To: <20151024233554.244e404b@debian-netbook>
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
next prev parent reply other threads:[~2015-10-25 17:18 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
2015-10-25 12:35 ` Aljosha Papsch [this message]
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=562CCC8A.80407@rpapsch.de \
--to=lists@rpapsch.de \
--cc=21720@debbugs.gnu.org \
--cc=efraim@flashner.co.il \
/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.