From: "Arsen Arsenović" <arsen@aarsen.me>
To: gcc-patches@gcc.gnu.org
Cc: libstdc++@gcc.gnu.org, "Arsen Arsenović" <arsen@aarsen.me>
Subject: Ping: [PATCH] libstdc++: Enable building libstdc++.{a,so} when !HOSTED
Date: Mon, 14 Nov 2022 19:34:16 +0100 [thread overview]
Message-ID: <86o7t9v0fh.fsf@aarsen.me> (raw)
In-Reply-To: <20221020154948.2511787-1-arsen@aarsen.me>
[-- Attachment #1: Type: text/plain, Size: 224 bytes --]
Evening,
Since S1 is closed now, best to ping this patch before it drifts into
GCC14.
Archive link:
https://gcc.gnu.org/pipermail/gcc-patches/2022-October/604031.html
Have a great evening!
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
next prev parent reply other threads:[~2022-11-14 18:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 15:49 Arsen Arsenović
2022-11-14 18:34 ` Arsen Arsenović [this message]
2022-11-15 15:58 ` Jonathan Wakely
2022-11-15 18:03 ` Arsen Arsenović
2023-02-06 14:24 ` Jonathan Wakely
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=86o7t9v0fh.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=gcc-patches@gcc.gnu.org \
--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).