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++/103650] [9/10/11/12 Regression] libstdc++ headers defined LT_OBJDIR and STDC_HEADERS Date: Mon, 17 Jan 2022 12:10:29 +0000 [thread overview] Message-ID: <bug-103650-4-qu0EGViULx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103650-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103650 --- Comment #1 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:fa092570fbaf3bb4202e518eb8beba146c464d9f commit r12-6633-gfa092570fbaf3bb4202e518eb8beba146c464d9f Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Jan 17 11:24:35 2022 +0000 libstdc++: Rename non-reserved macros in config header [PR103650] libstdc++-v3/ChangeLog: PR libstdc++/103650 * include/Makefile.am: Rename LT_OBJDIR and STDC_HEADERS. * include/Makefile.in: Regenerate. * testsuite/17_intro/headers/c++1998/103650.cc: New test.
next prev parent reply other threads:[~2022-01-17 12:10 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-10 14:49 [Bug libstdc++/103650] New: " redi at gcc dot gnu.org 2022-01-17 9:01 ` [Bug libstdc++/103650] " rguenth at gcc dot gnu.org 2022-01-17 12:10 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-04 11:47 ` [Bug libstdc++/103650] [9/10/11 " cvs-commit at gcc dot gnu.org 2022-04-04 21:22 ` [Bug libstdc++/103650] [9/10 " redi at gcc dot gnu.org 2022-04-26 13:12 ` cvs-commit at gcc dot gnu.org 2022-05-09 16:39 ` [Bug libstdc++/103650] [9 " cvs-commit at gcc dot gnu.org 2022-05-09 16:49 ` 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-103650-4-qu0EGViULx@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: linkBe 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).