From: David Craven <david@craven.ch>
To: guix-devel <guix-devel@gnu.org>
Subject: Re: GCC bootstrap failure on ARM
Date: Tue, 13 Sep 2016 08:11:22 +0200 [thread overview]
Message-ID: <CAL1_immnZCjFXCv+36GFbUCap6Gu8Gf92TDr-xenQxwospdB3g@mail.gmail.com> (raw)
In-Reply-To: <CAL1_imnQFeTU52eWJt6kcwzuCFmP6Si-y0kdPm9SmZyprkm5NA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 254 bytes --]
> ‘core-updates’ is now building with a tiny patch on gcc-4.9 (in fact
> it’s enough to apply it to gcc-cross-boot0, which is interesting):
Does this also fix the bootstrap failure with gcc 5? Or is that too late
for this core-updates cycle?
[-- Attachment #2: Type: text/html, Size: 295 bytes --]
next prev parent reply other threads:[~2016-09-13 6:12 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 8:59 Freezing core-updates Ludovic Courtès
2016-05-17 11:29 ` Leo Famulari
2016-05-17 21:21 ` Ludovic Courtès
[not found] ` <D79FF867-A6E4-480B-8D0C-FD597A836F6E@famulari.name>
2016-05-17 11:47 ` Leo Famulari
2016-05-17 12:03 ` Matthew Jordan
2016-05-17 12:11 ` Ben Woodcroft
2016-05-17 21:22 ` Ludovic Courtès
2016-05-26 16:59 ` Andreas Enge
2016-05-28 15:25 ` Ludovic Courtès
2016-05-31 19:33 ` Andreas Enge
2016-05-31 21:36 ` Ludovic Courtès
2016-06-01 9:41 ` Andreas Enge
2016-06-02 8:09 ` Ludovic Courtès
2016-06-04 15:33 ` Andreas Enge
2016-06-01 12:23 ` GCC bootstrap failure on ARM Ludovic Courtès
2016-06-01 18:45 ` Andreas Enge
2016-06-06 9:22 ` Ludovic Courtès
2016-06-07 9:58 ` Ludovic Courtès
2016-06-07 16:04 ` Leo Famulari
2016-06-08 0:55 ` Leo Famulari
2016-06-10 9:13 ` Andreas Enge
2016-06-10 12:16 ` Efraim Flashner
2016-06-10 12:22 ` Efraim Flashner
2016-08-21 2:55 ` Mark H Weaver
2016-08-21 11:44 ` David Craven
2016-08-21 12:17 ` David Craven
2016-08-21 12:26 ` Andreas Enge
2016-08-21 20:24 ` Mark H Weaver
2016-08-22 0:14 ` David Craven
2016-08-29 15:23 ` Ludovic Courtès
2016-09-10 13:16 ` Ludovic Courtès
2016-09-10 13:22 ` David Craven
2016-09-12 21:17 ` Ludovic Courtès
[not found] ` <CAL1_imniMsSJd+K=BTda+whFTKaErzwa+qSaUE0qeF=zA-Jv6A@mail.gmail.com>
[not found] ` <CAL1_imnQFeTU52eWJt6kcwzuCFmP6Si-y0kdPm9SmZyprkm5NA@mail.gmail.com>
2016-09-13 6:11 ` David Craven [this message]
2016-09-13 8:23 ` Ludovic Courtès
2016-09-13 8:26 ` Binutils build failure on MIPS Ludovic Courtès
2016-09-13 9:05 ` Vincent Legoll
2016-09-13 9:14 ` Vincent Legoll
2016-09-13 12:45 ` Ludovic Courtès
2016-09-13 14:00 ` Vincent Legoll
2016-09-13 14:05 ` David Craven
2016-09-13 14:19 ` Vincent Legoll
2016-09-13 14:27 ` David Craven
2016-09-13 14:36 ` Vincent Legoll
2016-09-13 22:02 ` Ludovic Courtès
2016-09-18 18:47 ` Andreas Enge
2016-09-21 16:02 ` Ludovic Courtès
2016-09-28 20:48 ` 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=CAL1_immnZCjFXCv+36GFbUCap6Gu8Gf92TDr-xenQxwospdB3g@mail.gmail.com \
--to=david@craven.ch \
--cc=guix-devel@gnu.org \
/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).