From: "H.J. Lu" <hjl.tools@gmail.com>
To: "Martin Liška" <mliska@suse.cz>
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 05:42:53 -0800 [thread overview]
Message-ID: <CAMe9rOqhRmXAwb-8LNOsZWWWUjOECuyB1_p_iiEpyFc8SgUs0Q@mail.gmail.com> (raw)
In-Reply-To: <c15c52de-69f4-c112-a217-f96559927d03@suse.cz>
On Fri, Nov 20, 2020 at 5:24 AM Martin Liška <mliska@suse.cz> wrote:
>
> Hello.
>
> I hit the following issue:
> /bin/sh /home/marxin/Programming/gcc/gcc/../move-if-change tmp-tm.texi tm.texi
> You should edit /home/marxin/Programming/gcc/gcc/doc/tm.texi.in rather than /home/marxin/Programming/gcc/gcc/doc/tm.texi .
>
> Steps to reproduce:
> 1) modify target.def
> 2) you will see:
>
> Verify that you have permission to grant a GFDL license for all
> new text in /dev/shm/objdir/gcc/tm.texi, then copy it to /home/marxin/Programming/gcc/gcc/doc/tm.texi.
>
> I copy and commit the changes.
>
> 3) I made another modification to target.def
>
> Now I face the issue as
> elif test $(srcdir)/doc/tm.texi -nt $(srcdir)/doc/tm.texi.in \
> && ( test $(srcdir)/doc/tm.texi -nt $(srcdir)/target.def \
>
> So tm.texi.in is older that tm.texi, but it's fine as both tm.texi.in
> and tm.texi are not modified.
>
> Ideas how to improve the error message? It took me some time to realize
> that 'touch tm.texi.in' is what I need.
Should contrib/gcc_update handle it?
--
H.J.
next prev parent reply other threads:[~2020-11-20 13:43 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 [this message]
2020-11-20 15:26 ` Martin Liška
2020-11-20 15:30 ` Martin Liška
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=CAMe9rOqhRmXAwb-8LNOsZWWWUjOECuyB1_p_iiEpyFc8SgUs0Q@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=mliska@suse.cz \
/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).