From: "Arsen Arsenović" <arsen@aarsen.me>
To: gcc-patches@gcc.gnu.org
Cc: "Gerald Pfeifer" <gerald@pfeifer.com>,
"Arsen Arsenović" <arsen@aarsen.me>
Subject: [PATCH] update_web_docs_git: Add updated Texinfo to PATH
Date: Thu, 6 Apr 2023 12:35:34 +0200 [thread overview]
Message-ID: <20230406103533.1087349-1-arsen@aarsen.me> (raw)
maintainer-scripts/ChangeLog:
* update_web_docs_git: Add updated Texinfo to PATH
---
Hi,
I'm posting this as a ping and a patch necessary to get the wwwdocs
building with the new Texinfo version that's installed on gcc.gnu.org.
It would be nice to do this ahead of the GCC 13 release.
I must ask that whoever decides to apply/update the script tests
texi2any with a simple example, like
echo @node Top | ~/texinfo/install-git/bin/makeinfo --html -o -
... before updating; this should be a representative enough smoke test.
You should see some HTML output with little text in it.
It might also be wise to test the script directly by using a different
WWWBASE, just in case, even though it should be safe.
Thanks in advance, have a lovely day.
maintainer-scripts/update_web_docs_git | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/maintainer-scripts/update_web_docs_git b/maintainer-scripts/update_web_docs_git
index d44ab27c1b7..f9006b1f45b 100755
--- a/maintainer-scripts/update_web_docs_git
+++ b/maintainer-scripts/update_web_docs_git
@@ -12,7 +12,7 @@ set -e
GITROOT=${GITROOT:-"/git/gcc.git"}
export GITROOT
-PATH=/usr/local/bin:$PATH
+PATH=/home/gccadmin/texinfo/install-git/bin:/usr/local/bin:$PATH
MANUALS="cpp
cppinternals
--
2.40.0
next reply other threads:[~2023-04-06 10:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 10:35 Arsen Arsenović [this message]
2023-04-10 21:45 ` Gerald Pfeifer
2023-04-10 22:15 ` Arsen Arsenović
2023-04-14 19:29 ` Gerald Pfeifer
2023-04-14 20:25 ` Arsen Arsenović
2023-04-20 20:14 ` Gerald Pfeifer
2023-04-20 20:53 ` Arsen Arsenović
2023-04-21 7:00 ` Gerald Pfeifer
2023-04-21 8:46 ` Arsen Arsenović
2023-04-10 21:49 ` Gerald Pfeifer
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=20230406103533.1087349-1-arsen@aarsen.me \
--to=arsen@aarsen.me \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
/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).