public inbox for gcc-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 r14-3789] libstdc++: Fix 'doc-install-info' rule
Date: Thu,  7 Sep 2023 16:54:18 +0000 (GMT)	[thread overview]
Message-ID: <20230907165418.219393858D20@sourceware.org> (raw)

https://gcc.gnu.org/g:09c2815dc1665cd1cff96487f2e5bb368ccc3185

commit r14-3789-g09c2815dc1665cd1cff96487f2e5bb368ccc3185
Author: Bruno Victal <mirai@makinata.eu>
Date:   Mon Aug 21 21:34:02 2023 +0100

    libstdc++: Fix 'doc-install-info' rule
    
    The info manual isn't moved to the expected location after
    generation which causes the install rule for it to fail.
    
    libstdc++-v3/Changelog:
    
            * doc/Makefile.am: Fix 'doc-install-info' rule.
            Fix typo in commment.
            * doc/Makefile.in: Regenerate.

Diff:
---
 libstdc++-v3/doc/Makefile.am | 4 ++--
 libstdc++-v3/doc/Makefile.in | 4 ++--
 2 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/libstdc++-v3/doc/Makefile.am b/libstdc++-v3/doc/Makefile.am
index 8371441c62e1..373522d593d9 100644
--- a/libstdc++-v3/doc/Makefile.am
+++ b/libstdc++-v3/doc/Makefile.am
@@ -598,7 +598,7 @@ stamp-pdf-docbook: doc-pdf-docbook-pre doc-xml-single-docbook
 doc-pdf-docbook: stamp-pdf-docbook
 
 # TEXINFO, via docbook2X
-# NB: Both experimental and tempermental
+# NB: Both experimental and temperamental
 manual_texi = ${docbook_outdir}/texinfo/libstdc++-manual.texi
 manual_info = ${docbook_outdir}/texinfo/libstdc++-manual.info
 DB2TEXI_FLAGS = \
@@ -615,7 +615,7 @@ stamp-texinfo-docbook: stamp-xml-single-docbook ${docbook_outdir}/texinfo
 
 stamp-info-docbook: stamp-texinfo-docbook
 	@echo "Generating info files..."
-	$(MAKEINFO) $(MAKEINFOFLAGS) ${manual_texi}
+	$(MAKEINFO) $(MAKEINFOFLAGS) ${manual_texi} -o ${manual_info}
 	$(STAMP) stamp-info-docbook
 
 doc-texinfo-docbook: stamp-texinfo-docbook
diff --git a/libstdc++-v3/doc/Makefile.in b/libstdc++-v3/doc/Makefile.in
index 21ad8557f7a8..c19e3e3044c8 100644
--- a/libstdc++-v3/doc/Makefile.in
+++ b/libstdc++-v3/doc/Makefile.in
@@ -645,7 +645,7 @@ manual_pdf = ${docbook_outdir}/pdf/libstdc++-manual.pdf
 DBLATEX_FLAGS = --verbose --pdf --dump --debug --tmpdir=${docbook_outdir}/latex
 
 # TEXINFO, via docbook2X
-# NB: Both experimental and tempermental
+# NB: Both experimental and temperamental
 manual_texi = ${docbook_outdir}/texinfo/libstdc++-manual.texi
 manual_info = ${docbook_outdir}/texinfo/libstdc++-manual.info
 DB2TEXI_FLAGS = \
@@ -1096,7 +1096,7 @@ stamp-texinfo-docbook: stamp-xml-single-docbook ${docbook_outdir}/texinfo
 
 stamp-info-docbook: stamp-texinfo-docbook
 	@echo "Generating info files..."
-	$(MAKEINFO) $(MAKEINFOFLAGS) ${manual_texi}
+	$(MAKEINFO) $(MAKEINFOFLAGS) ${manual_texi} -o ${manual_info}
 	$(STAMP) stamp-info-docbook
 
 doc-texinfo-docbook: stamp-texinfo-docbook

                 reply	other threads:[~2023-09-07 16:54 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=20230907165418.219393858D20@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).