From: Bruno Victal <mirai@makinata.eu>
To: gcc-patches@gcc.gnu.org
Cc: libstdc++@gcc.gnu.org, Bruno Victal <mirai@makinata.eu>
Subject: [PATCH 1/2] libstdc++: Fix 'doc-install-info' rule.
Date: Mon, 21 Aug 2023 21:34:02 +0100 [thread overview]
Message-ID: <fa9724f1b198f6416bb8e05966f57b0742201b73.1692650021.git.mirai@makinata.eu> (raw)
In-Reply-To: <cover.1692649706.git.mirai@makinata.eu>
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.in: Regenerate.
* doc/Makefile.am: Fix 'doc-install-info' rule.
Fix typo in commment.
---
libstdc++-v3/doc/Makefile.am | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/libstdc++-v3/doc/Makefile.am b/libstdc++-v3/doc/Makefile.am
index 8371441c62e..373522d593d 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
base-commit: f9ff6fa58217294d63f255dd02abfcc8a074f509
--
2.40.1
next prev parent reply other threads:[~2023-08-21 20:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 20:31 [PATCH 0/2] libstdc++: Documentation fixes Bruno Victal
2023-08-21 20:34 ` Bruno Victal [this message]
2023-08-21 20:34 ` [PATCH 2/2] libstdc++: Update docbook xsl URI Bruno Victal
2023-08-21 20:40 ` [PATCH 0/2] libstdc++: Documentation fixes Jonathan Wakely
2023-09-07 16:54 ` Jonathan Wakely
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=fa9724f1b198f6416bb8e05966f57b0742201b73.1692650021.git.mirai@makinata.eu \
--to=mirai@makinata.eu \
--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).