From: Stephan Bergmann <sbergman@redhat.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: libstdc++ <libstdc++@gcc.gnu.org>, gcc Patches <gcc-patches@gcc.gnu.org>
Subject: Re: trunk -D_GLIBCXX_DEBUG #include <regex> fails
Date: Tue, 10 Aug 2021 09:24:21 +0200 [thread overview]
Message-ID: <ddafc1e7-7349-adbd-e4f1-403ea722cf99@redhat.com> (raw)
In-Reply-To: <CACb0b4kUpkn06+wvUu3k1h_jCRPqB-iaM7x3oez5Y+MTJnc0-Q@mail.gmail.com>
On 09/08/2021 16:42, Jonathan Wakely via Gcc-patches wrote:
> This is what I'm testing.
Thanks, that worked fine for my build of LibreOffice.
prev parent reply other threads:[~2021-08-10 7:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 9:50 Stephan Bergmann
2021-08-09 10:05 ` Jonathan Wakely
2021-08-09 12:05 ` François Dumont
2021-08-09 14:27 ` Jonathan Wakely
2021-08-09 14:42 ` Jonathan Wakely
2021-08-09 19:47 ` Jonathan Wakely
2021-08-10 7:24 ` Stephan Bergmann [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=ddafc1e7-7349-adbd-e4f1-403ea722cf99@redhat.com \
--to=sbergman@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@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).