From: Efraim Flashner <efraim@flashner.co.il>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: 23/33: gnu: commencement: gcc-boot0: Build fix for the Hurd.
Date: Wed, 11 Mar 2020 16:27:25 +0000 [thread overview]
Message-ID: <6E631CC8-3381-4172-9825-308659BBA5B5@flashner.co.il> (raw)
In-Reply-To: <87d09iualx.fsf@gnu.org>
On March 11, 2020 4:20:26 PM UTC, Jan Nieuwenhuizen <janneke@gnu.org> wrote:
>Efraim Flashner writes:
>
>> If you're using gcc-7 as the bootstrap gcc for the Hurd then IMO you
>> should go ahead and either use gcc-7 or gcc for the libstdc++-boot0
>
>Ah...your patch but then with gcc-7 instead of gcc-5; gosh why didn't I
>think of that. Thank you!
>
>I'll give that a try...although that patch won't get in, in its current
>form, right? We'd have to think of some solution...
>
>janneke
>
For new architectures it can go in, but there's no actual need for it for aarch64
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
next prev parent reply other threads:[~2020-03-11 16:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200310075832.7126.86402@vcs0.savannah.gnu.org>
[not found] ` <20200310075845.291F421123@vcs0.savannah.gnu.org>
2020-03-10 8:54 ` 08/33: gnu: make: Revert to 4.1 for the Hurd Ludovic Courtès
2020-03-10 9:16 ` Jan Nieuwenhuizen
[not found] ` <20200310075844.240A021123@vcs0.savannah.gnu.org>
2020-03-10 8:55 ` 05/33: gnu: hurd: Fix hurd-target? Ludovic Courtès
2020-03-10 11:22 ` Jan Nieuwenhuizen
[not found] ` <20200310075846.1DA6821123@vcs0.savannah.gnu.org>
2020-03-10 9:02 ` 11/33: gnu: glibc: Add and update patches for the Hurd Ludovic Courtès
2020-03-10 11:28 ` Jan Nieuwenhuizen
[not found] ` <20200310075853.45FCC21252@vcs0.savannah.gnu.org>
2020-03-10 9:04 ` 33/33: daemon: Workaround issues " Ludovic Courtès
2020-03-10 12:54 ` Jan Nieuwenhuizen
2020-03-11 14:50 ` Ludovic Courtès
2020-03-12 6:59 ` Jan Nieuwenhuizen
2020-03-12 12:59 ` Ludovic Courtès
[not found] ` <20200310075847.6059A2112F@vcs0.savannah.gnu.org>
2020-03-10 9:06 ` 15/33: gnu: coreutils: Remove libcap dependency " Ludovic Courtès
2020-03-11 15:01 ` Jan Nieuwenhuizen
2020-03-11 18:09 ` Vincent Legoll
2020-03-11 19:43 ` Jan Nieuwenhuizen
2020-03-12 13:01 ` Ludovic Courtès
2020-03-14 8:28 ` Jan Nieuwenhuizen
[not found] ` <20200310075851.4497E2125F@vcs0.savannah.gnu.org>
2020-03-10 9:10 ` 27/33: gnu: commencement: glibc-intermediate: Build fixes " Ludovic Courtès
2020-03-10 12:45 ` Jan Nieuwenhuizen
[not found] ` <20200310075850.035F02125B@vcs0.savannah.gnu.org>
2020-03-10 9:13 ` 23/33: gnu: commencement: gcc-boot0: Build fix " Ludovic Courtès
2020-03-10 9:18 ` Efraim Flashner
2020-03-10 13:53 ` Jan Nieuwenhuizen
2020-03-11 14:27 ` Jan Nieuwenhuizen
2020-03-11 15:14 ` Efraim Flashner
2020-03-11 16:20 ` Jan Nieuwenhuizen
2020-03-11 16:27 ` Efraim Flashner [this message]
2020-03-12 7:02 ` Jan Nieuwenhuizen
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=6E631CC8-3381-4172-9825-308659BBA5B5@flashner.co.il \
--to=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--cc=janneke@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).