From: "Martin Liška" <mliska@suse.cz>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: broken check: You should edit tm.texi.in rather than tm.texi
Date: Fri, 20 Nov 2020 16:30:48 +0100 [thread overview]
Message-ID: <23003777-506c-b846-6a2e-44d9bc2579fd@suse.cz> (raw)
In-Reply-To: <58139863-7a76-dae6-e3bf-e4b26c477a89@suse.cz>
On 11/20/20 4:26 PM, Martin Liška wrote:
> On 11/20/20 2:42 PM, H.J. Lu wrote:
>> Should contrib/gcc_update handle it?
>
> I don't know how publicly known is the script?
> I personally do not used it.
>
> Martin
... or we can add a hint:
diff --git a/gcc/Makefile.in b/gcc/Makefile.in
index 778ec09c75d..f079930dade 100644
--- a/gcc/Makefile.in
+++ b/gcc/Makefile.in
@@ -2580,6 +2580,7 @@ s-tm-texi: build/genhooks$(build_exeext) $(srcdir)/doc/tm.texi.in
); then \
echo >&2 ; \
echo You should edit $(srcdir)/doc/tm.texi.in rather than $(srcdir)/doc/tm.texi . >&2 ; \
+ echo "(or you may need to touch $(srcdir)/doc/tm.texi.in if $(srcdir)/doc/tm.texi is not modified)" >&2 ; \
false; \
else \
echo >&2 ; \
Thoughs?
Martin
next prev parent reply other threads:[~2020-11-20 15:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 13:23 Martin Liška
2020-11-20 13:42 ` H.J. Lu
2020-11-20 15:26 ` Martin Liška
2020-11-20 15:30 ` Martin Liška [this message]
2020-11-20 15:34 ` H.J. Lu
2020-11-23 19:06 ` Martin Sebor
2020-11-23 19:45 ` Joseph Myers
2020-11-23 20:13 ` Martin Sebor
2020-11-23 20:25 ` Joseph Myers
2020-11-23 21:04 ` Martin Sebor
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=23003777-506c-b846-6a2e-44d9bc2579fd@suse.cz \
--to=mliska@suse.cz \
--cc=gcc@gcc.gnu.org \
--cc=hjl.tools@gmail.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).