From: Olivier Hainque <hainque@adacore.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Olivier Hainque <hainque@adacore.com>,
libstdc++ <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [patch] configury support for VxWorks shared libraries
Date: Tue, 11 Oct 2022 09:26:26 +0200 [thread overview]
Message-ID: <2BDDD868-8FB8-4F17-A2DD-261570D0D860@adacore.com> (raw)
In-Reply-To: <CACb0b4m8uDRPSoS8M=_44aDdz4Ey8GLYiqaE5wwC4A+U7t9_8A@mail.gmail.com>
> On 10 Oct 2022, at 21:38, Jonathan Wakely <jwakely@redhat.com> wrote:
>
> On Mon, 10 Oct 2022 at 19:06, Olivier Hainque via Libstdc++
> <libstdc++@gcc.gnu.org> wrote:
>>
>> Sorry, I forgot to cc libstdc++ on
>>
>> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/603182.html
>>
>> which includes a regen of libstdc++-v3/configure after an update
>> libtool.m4.
>
> OK,
Great :)
> thanks for the heads up.
You are very welcome. Thanks for your prompt feedback.
Regards,
Olivier
prev parent reply other threads:[~2022-10-11 7:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1CD1BBE-3782-4712-846D-B5A877630BE7@adacore.com>
2022-10-10 18:05 ` Olivier Hainque
2022-10-10 19:38 ` Jonathan Wakely
2022-10-11 7:26 ` Olivier Hainque [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=2BDDD868-8FB8-4F17-A2DD-261570D0D860@adacore.com \
--to=hainque@adacore.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).