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: Wed, 21 Oct 2015 18:38:17 +0200 [thread overview]
Message-ID: <874mhkb2iu.fsf@gnu.org> (raw)
In-Reply-To: <1445361729.24180.0@ara.uberspace.de> (Aljosha Papsch's message of "Tue, 20 Oct 2015 19:22:09 +0200")
Aljosha Papsch <lists@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’.
next prev parent reply other threads:[~2015-10-21 16:39 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 [this message]
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
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874mhkb2iu.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).