From: Jonathan Wakely <jwakely@redhat.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: [committed] libstdc++: Fix example preprocessor command in FAQ [PR103877]
Date: Wed, 5 Jan 2022 13:48:05 +0000 [thread overview]
Message-ID: <20220105134805.1639875-1-jwakely@redhat.com> (raw)
Tested powerpc64le-linux, pushed to trunk.
libstdc++-v3/ChangeLog:
PR libstdc++/103877
* doc/xml/faq.xml: Add '-x c++' to preprocessor command.
* doc/html/faq.html: Regenerate.
---
libstdc++-v3/doc/html/faq.html | 2 +-
libstdc++-v3/doc/xml/faq.xml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/libstdc++-v3/doc/html/faq.html b/libstdc++-v3/doc/html/faq.html
index 967e5f5f348..f49b84c4c33 100644
--- a/libstdc++-v3/doc/html/faq.html
+++ b/libstdc++-v3/doc/html/faq.html
@@ -456,7 +456,7 @@
<code class="varname">CPLUSPLUS_CPP_SPEC</code> in
the gcc config headers for your target (and try changing them to
see what happens when building complicated code). You can also run
- <span class="command"><strong>g++ -E -dM - < /dev/null"</strong></span> to display
+ <span class="command"><strong>g++ -E -dM -x c++ /dev/null</strong></span> to display
a list of predefined macros for any particular installation.
</p><p>This has been discussed on the mailing lists
<a class="link" href="http://gcc.gnu.org/cgi-bin/htsearch?method=and&format=builtin-long&sort=score&words=_XOPEN_SOURCE+Solaris" target="_top">quite a bit</a>.
diff --git a/libstdc++-v3/doc/xml/faq.xml b/libstdc++-v3/doc/xml/faq.xml
index e419d3c22a0..9ae4966ecea 100644
--- a/libstdc++-v3/doc/xml/faq.xml
+++ b/libstdc++-v3/doc/xml/faq.xml
@@ -580,7 +580,7 @@
<varname>CPLUSPLUS_CPP_SPEC</varname> in
the gcc config headers for your target (and try changing them to
see what happens when building complicated code). You can also run
- <command>g++ -E -dM - < /dev/null"</command> to display
+ <command>g++ -E -dM -x c++ /dev/null</command> to display
a list of predefined macros for any particular installation.
</para>
<para>This has been discussed on the mailing lists
--
2.31.1
reply other threads:[~2022-01-05 13:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220105134805.1639875-1-jwakely@redhat.com \
--to=jwakely@redhat.com \
--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).