From: ludo@gnu.org (Ludovic Courtès)
To: Aljosha Papsch <lists@rpapsch.de>
Cc: 21720@debbugs.gnu.org
Subject: bug#21720: Building gcc fails at target s-attrtab
Date: Sun, 25 Oct 2015 22:05:07 +0100 [thread overview]
Message-ID: <87io5umzgc.fsf@gnu.org> (raw)
In-Reply-To: <56296B65.8000407@rpapsch.de> (Aljosha Papsch's message of "Fri, 23 Oct 2015 01:04:05 +0200")
Aljosha Papsch <lists@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’.
prev parent reply other threads:[~2015-10-25 21:06 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
2015-10-25 13:25 ` Efraim Flashner
2015-10-25 21:06 ` Ludovic Courtès
2015-10-25 21:05 ` Ludovic Courtès [this message]
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=87io5umzgc.fsf@gnu.org \
--to=ludo@gnu.org \
--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.