public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r9-10054] libstdc++: Fix example preprocessor command in FAQ [PR103877]
Date: Mon,  9 May 2022 16:39:49 +0000 (GMT)	[thread overview]
Message-ID: <20220509163949.BEB7D385735C@sourceware.org> (raw)

https://gcc.gnu.org/g:dae73190d42a8074cc393c759338942d0de8b2bd

commit r9-10054-gdae73190d42a8074cc393c759338942d0de8b2bd
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Jan 4 15:54:16 2022 +0000

    libstdc++: Fix example preprocessor command in FAQ [PR103877]
    
    libstdc++-v3/ChangeLog:
    
            PR libstdc++/103877
            * doc/xml/faq.xml: Add '-x c++' to preprocessor command.
            * doc/html/faq.html: Regenerate.
    
    (cherry picked from commit cebe875f6f44b905a0d56a2007b5a638a33a893c)

Diff:
---
 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 18407225d7a..aa85d85db46 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 - &lt; /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&amp;format=builtin-long&amp;sort=score&amp;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 cf8684e1cea..ef673ef4954 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 - &lt; /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


                 reply	other threads:[~2022-05-09 16:39 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=20220509163949.BEB7D385735C@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).