public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/106953] C++23 add new headers for freestanding
Date: Mon, 03 Oct 2022 14:45:52 +0000 [thread overview]
Message-ID: <bug-106953-4-dCa3VFoLaI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106953-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106953
--- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:
https://gcc.gnu.org/g:6885e7e4eef65c657cd8baa0f5e7ebe7231ac984
commit r13-3038-g6885e7e4eef65c657cd8baa0f5e7ebe7231ac984
Author: Arsen ArsenoviÄ <arsen@aarsen.me>
Date: Fri Sep 16 10:38:41 2022 +0200
libstdc++: Rework how freestanding install works [PR106953]
In light of there being far more freestanding headers now, ad-hoc
maintenance of a subset of the install implementation has become
unsustainable. Instead, we gate off a part of the normal install routine
so that it works without HOSTED enabled, as well as subdivide lists of
headers into freestanding and hosted components, according to the HOSTED
flag.
libstdc++-v3/ChangeLog:
PR libstdc++/106953
* include/Makefile.am [!_GLIBCXX_HOSTED]: Remove
install-freestanding-headers, unifying it with the usual
install-headers
* include/Makefile.in: Regenerate.
next prev parent reply other threads:[~2022-10-03 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-16 8:39 [Bug libstdc++/106953] New: " unlvsur at live dot com
2022-09-16 8:53 ` [Bug libstdc++/106953] " redi at gcc dot gnu.org
2022-09-16 22:33 ` cvs-commit at gcc dot gnu.org
2022-09-17 3:28 ` unlvsur at live dot com
2022-09-17 3:29 ` unlvsur at live dot com
2022-09-20 9:54 ` redi at gcc dot gnu.org
2022-10-03 14:45 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-03 14:51 ` redi at gcc dot gnu.org
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=bug-106953-4-dCa3VFoLaI@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).