From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Thomas Schwinge <thomas@codesourcery.com>
Cc: "Flávio Cruz" <flaviocruz@gmail.com>,
gcc-patches@gcc.gnu.org, bug-hurd@gnu.org
Subject: Re: [PATCH] Add support for x86_64-*-gnu-* targets to build x86_64 gnumach/hurd
Date: Wed, 1 Feb 2023 19:19:10 +0100 [thread overview]
Message-ID: <20230201181910.ya2veg5bw5cm5clr@lug-owl.de> (raw)
In-Reply-To: <87zga0yqle.fsf@dem-tschwing-1.ger.mentorg.com>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
Hi Flávio and Thomas!
On Mon, 2023-01-30 16:44:29 +0100, Thomas Schwinge <thomas@codesourcery.com> wrote:
> On 2023-01-27T21:15:01-0500, Flávio Cruz <flaviocruz@gmail.com> wrote:
> > Not sure what happened, but here's the patch as an attachment. Thanks for
> > your patience.
>
> Thanks, that worked. Without any changes now pushed to master branch in
> commit 5f8950b403f6351f125d8281d2e7430a43e7d125
> "Add support for x86_64-*-gnu-* targets to build x86_64 gnumach/hurd",
> see attached.
>
> I'll watch how x86_64 GNU/Hurd develops! :-)
Please also add this target configuration to contrib/config-list.mk
Thanks,
Jan-Benedict
--
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2023-02-01 18:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Y6DgFCo4mEzztu+Q@mars>
2022-12-26 17:34 ` Flavio Cruz
2023-01-09 18:00 ` Flávio Cruz
2023-01-25 15:56 ` Flávio Cruz
2023-01-26 8:34 ` Thomas Schwinge
2023-01-27 6:49 ` Flavio Cruz
[not found] ` <875ycr1xwp.fsf@dem-tschwing-1.ger.mentorg.com>
[not found] ` <CAKwpGPwYX77GbZk=TiD73AFs8+KvQrZ-8nkArQ_H=R9hiC_Pfg@mail.gmail.com>
2023-01-30 15:44 ` Thomas Schwinge
2023-02-01 18:19 ` Jan-Benedict Glaw [this message]
2023-02-02 5:55 ` [PATCH] Add x86_64-gnu target to contrib/config-list.mk Flavio Cruz
2023-02-10 10:05 ` Thomas Schwinge
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=20230201181910.ya2veg5bw5cm5clr@lug-owl.de \
--to=jbglaw@lug-owl.de \
--cc=bug-hurd@gnu.org \
--cc=flaviocruz@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=thomas@codesourcery.com \
/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.
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).