From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: GCC bootstrap failure on ARM
Date: Sat, 10 Sep 2016 15:16:02 +0200 [thread overview]
Message-ID: <8760q3opyl.fsf@gnu.org> (raw)
In-Reply-To: <87bn0b1two.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Mon, 29 Aug 2016 17:23:03 +0200")
ludo@gnu.org (Ludovic Courtès) skribis:
> Mark H Weaver <mhw@netris.org> skribis:
>
>> David Craven <david@craven.ch> writes:
>>
>>> I can help fixing package regressions if someone gets the ball
>>> rolling. Is there a reason to upgrade to gcc 5 or does it make sense
>>> to jump to gcc 6 directly? If I understand correctly most of the work
>>> required for an update to gcc 5 has already been done?
>>
>> Until the bootstrapping problem on ARM is fixed, we can't do any of
>> this. At the moment, that's blocking us from even updating to 4.9.4,
>> nevermind 5 or 6. If you want to help us upgrade our default GCC,
>> investigating that problem would be the best way.
>
> It might be that fixing bootstrap with GCC 5 (or 6) or ARM wouldn’t be
> much harder than with 4.9.
>
> For the record, this is how far I got with GCC 5:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71399
I’ve made some progress on this, as reported on bugzilla. I’m now
trying to bisect the issue; however, since the bootstrapping failure of
gcc-final is due to a problem that manifests in gcc-boot0, that’s a lot
of rebuild, and the machine I’m using (redhill) is slow.
Anyway, we’ll have a patch reverting a few 4.9.3-to-4.9.4 commits, and
that’ll allow us to proceed. I’d like to reduce that patch as much as
possible, but I’d like to stop researching by the end of next week so we
can then freeze core-updates.
Ludo’.
next prev parent reply other threads:[~2016-09-10 13:16 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8760q3opyl.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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 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.