From: Alan Modra <amodra@gmail.com>
To: Nick Alcock <nick.alcock@oracle.com>
Cc: binutils@sourceware.org, Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH 1/8] intl: Allow building both with old bison and bison >= 3 [PR92008]
Date: Wed, 10 Feb 2021 18:33:13 +1030 [thread overview]
Message-ID: <20210210080313.GG5348@bubble.grove.modra.org> (raw)
In-Reply-To: <20210208111635.74970-2-nick.alcock@oracle.com>
On Mon, Feb 08, 2021 at 11:16:28AM +0000, Nick Alcock via Binutils wrote:
> [nca: sync from gcc]
This is fine.
--
Alan Modra
Australia Development Lab, IBM
next prev parent reply other threads:[~2021-02-10 8:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 11:16 [PATCH 0/8 RFC] unbreak --with-included-gettext, and other configury stuff Nick Alcock
2021-02-08 11:16 ` [PATCH 1/8] intl: Allow building both with old bison and bison >= 3 [PR92008] Nick Alcock
2021-02-10 8:03 ` Alan Modra [this message]
2021-02-08 11:16 ` [PATCH 2/8] intl: Unbreak intl build with bison 3 when no regeneration is needed [PR92008] Nick Alcock
2021-02-10 8:04 ` Alan Modra
2021-02-08 11:16 ` [PATCH 3/8] intl: always picify Nick Alcock
2021-02-08 11:16 ` [PATCH 4/8] intl: turn LIBINTL into -L / -l form Nick Alcock
2021-02-10 8:05 ` Alan Modra
2021-02-08 11:16 ` [PATCH 5/8] bfd, opcodes, libctf: support --with-included-gettext Nick Alcock
2021-02-10 8:06 ` Alan Modra
2021-02-08 11:16 ` [PATCH 6/8] gdbserver: explicitly include gettext, etc in inprocess agent Nick Alcock
2021-02-08 19:51 ` Tom Tromey
2021-02-08 20:51 ` Nick Alcock
2021-02-10 13:33 ` Nick Alcock
2021-02-08 11:16 ` [PATCH 7/8] libctf: require a Tcl capable of try/catch to run tests Nick Alcock
2021-02-08 11:16 ` [PATCH 8/8] libctf: add missing header in BFD ELF check Nick Alcock
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=20210210080313.GG5348@bubble.grove.modra.org \
--to=amodra@gmail.com \
--cc=binutils@sourceware.org \
--cc=jakub@redhat.com \
--cc=nick.alcock@oracle.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).