public inbox for gdb-testers@sourceware.org
help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net
To: gdb-testers@sourceware.org
Subject: [binutils-gdb] gdbserver: fix Makefile dependency of regformat-generated files on regdat.sh
Date: Mon, 13 Jan 2020 20:04:00 -0000	[thread overview]
Message-ID: <4025fa094d2420134acc4fea2049e707df8ecd01@gdb-build> (raw)

*** TEST RESULTS FOR COMMIT 4025fa094d2420134acc4fea2049e707df8ecd01 ***

commit 4025fa094d2420134acc4fea2049e707df8ecd01
Author:     Simon Marchi <simon.marchi@efficios.com>
AuthorDate: Mon Jan 13 13:57:32 2020 -0500
Commit:     Simon Marchi <simon.marchi@efficios.com>
CommitDate: Mon Jan 13 13:58:02 2020 -0500

    gdbserver: fix Makefile dependency of regformat-generated files on regdat.sh
    
    The intent of the rules modified by this patch is that the *-generated.c
    files generated by regdat.sh are re-generated in the event that
    regdat.sh is modified.  However, if I build, touch regdat.sh, and build
    again, the files are not re-generated during the second build.
    
    This is because regdat.sh is specified as an order-only dependency [1],
    after the pipe.  Make therefore only ensures that regdat.sh exists
    before generating the target file, it doesn't check the timestamp of
    regdat.sh.
    
    This patch changes it to be a regular prerequisite.
    
    The rules use the $< variable, which is substituted by the first
    prerequisite only, so the command lines won't change.
    
    [1] https://www.gnu.org/software/make/manual/html_node/Prerequisite-Types.html
    
    gdb/gdbserver/ChangeLog:
    
            * Makefile.in (%-generated.c): Make $(regdat_sh) a regular
            prerequisite.

diff --git a/gdb/gdbserver/ChangeLog b/gdb/gdbserver/ChangeLog
index 67d39beba5..730c53a2e8 100644
--- a/gdb/gdbserver/ChangeLog
+++ b/gdb/gdbserver/ChangeLog
@@ -1,3 +1,8 @@
+2020-01-13  Simon Marchi  <simon.marchi@efficios.com>
+
+	* Makefile.in (%-generated.c): Make $(regdat_sh) a regular
+	prerequisite.
+
 2020-01-12  Simon Marchi  <simon.marchi@polymtl.ca>
 
 	* linux-arm-tdesc.c: Include linux-arm-tdesc.h.
diff --git a/gdb/gdbserver/Makefile.in b/gdb/gdbserver/Makefile.in
index 1125426778..fd43e407b8 100644
--- a/gdb/gdbserver/Makefile.in
+++ b/gdb/gdbserver/Makefile.in
@@ -648,16 +648,16 @@ gdbsupport/%.o: ../gdbsupport/%.c
 # Rules for register format descriptions.  Suffix destination files with
 # -generated to identify and clean them easily.
 
-%-generated.c: ../regformats/%.dat | $(regdat_sh)
+%-generated.c: ../regformats/%.dat $(regdat_sh)
 	$(ECHO_REGDAT) $(SHELL) $(regdat_sh) $< $@
 
-%-generated.c: ../regformats/arm/%.dat | $(regdat_sh)
+%-generated.c: ../regformats/arm/%.dat $(regdat_sh)
 	$(ECHO_REGDAT) $(SHELL) $(regdat_sh) $< $@
 
-%-generated.c: ../regformats/i386/%.dat | $(regdat_sh)
+%-generated.c: ../regformats/i386/%.dat $(regdat_sh)
 	$(ECHO_REGDAT) $(SHELL) $(regdat_sh) $< $@
 
-%-generated.c: ../regformats/rs6000/%.dat | $(regdat_sh)
+%-generated.c: ../regformats/rs6000/%.dat $(regdat_sh)
 	$(ECHO_REGDAT) $(SHELL) $(regdat_sh) $< $@
 
 #


             reply	other threads:[~2020-01-13 19:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 20:04 gdb-buildbot [this message]
2020-01-13 19:56 ` Failures on Ubuntu-Aarch64-native-gdbserver-m64, branch master gdb-buildbot
2020-01-15 13:49 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot
2020-01-15 13:49 ` Failures on Fedora-x86_64-m32, " gdb-buildbot
2020-01-15 14:07 ` Failures on Fedora-x86_64-m64, " gdb-buildbot
2020-01-15 14:42 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot
2020-01-15 15:14 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot
2020-01-15 15:23 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot

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=4025fa094d2420134acc4fea2049e707df8ecd01@gdb-build \
    --to=gdb-buildbot@sergiodj.net \
    --cc=gdb-testers@sourceware.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).