From: Jonathan Wakely <jwakely@redhat.com>
To: Eric Botcazou <botcazou@adacore.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [committed] libstdc++: Test errno macros directly, not via autoconf [PR 93151]
Date: Thu, 1 Apr 2021 18:51:17 +0100 [thread overview]
Message-ID: <20210401175117.GW3008@redhat.com> (raw)
In-Reply-To: <1864695.yKVeVyVuyW@fomalhaut>
On 01/04/21 18:47 +0200, Eric Botcazou wrote:
>> Thanks, pushed.
>
>I can confirm that the build failure we had is now gone, thanks!
>
>> Eric, are you building the RC with --enable-maintainer-mode maybe? Or
>> regenerating the autoconf files yourself?
>
>The latter, we have local configure changes so we regenerate the script.
Aha, that explains it then. And it's useful that you noticed this
before the final release!
prev parent reply other threads:[~2021-04-01 17:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 13:38 Jonathan Wakely
2020-12-17 14:05 ` Jonathan Wakely
2020-12-17 16:21 ` Jonathan Wakely
2021-04-01 14:04 ` Eric Botcazou
2021-04-01 14:25 ` Jonathan Wakely
2021-04-01 14:27 ` Jakub Jelinek
2021-04-01 15:15 ` Jonathan Wakely
2021-04-01 16:47 ` Eric Botcazou
2021-04-01 17:51 ` Jonathan Wakely [this message]
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=20210401175117.GW3008@redhat.com \
--to=jwakely@redhat.com \
--cc=botcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=libstdc++@gcc.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.
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).