aboutsummaryrefslogtreecommitdiff
path: root/gdb/Makefile.in
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2020-10-30 10:27:12 -0600
committerTom Tromey <tromey@adacore.com>2020-10-30 12:31:29 -0600
commitb1ec273502937ca128df0ebf3e5961731fdc7272 (patch)
treef6962011d769ab7b0cc10525e7dc4ee195d90d49 /gdb/Makefile.in
parentb8fd9b80eedff9339b9374c6dcef633be88c5b9e (diff)
downloadgdb-b1ec273502937ca128df0ebf3e5961731fdc7272.zip
gdb-b1ec273502937ca128df0ebf3e5961731fdc7272.tar.gz
gdb-b1ec273502937ca128df0ebf3e5961731fdc7272.tar.bz2
Have stamp-init depend on config.status
I recently wrote a patch to modify configure.tgt. However, I did this incorrectly the first time, and had to go back and add another file. After building, I was surprised that my changes did not seem to work. I tracked this down to the fact that init.c had not been rebuilt after my changes -- because the files I added to the build were already older than the existing init.c. This patch changes the gdb Makefile so that init.c will be rebuilt if config.status changes. This should cover various scenarios that cause a re-configure, like editing configure.tgt. 2020-10-30 Tom Tromey <tromey@adacore.com> * Makefile.in (stamp-init): Depend on config.status.
Diffstat (limited to 'gdb/Makefile.in')
-rw-r--r--gdb/Makefile.in2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/Makefile.in b/gdb/Makefile.in
index 8a16089..b3be21b 100644
--- a/gdb/Makefile.in
+++ b/gdb/Makefile.in
@@ -1833,7 +1833,7 @@ INIT_FILES = \
$(COMMON_OBS))))
init.c: stamp-init; @true
-stamp-init: $(INIT_FILES)
+stamp-init: $(INIT_FILES) config.status
@$(ECHO_INIT_C) echo "Making init.c"
@rm -f init.c-tmp init.l-tmp
@touch init.c-tmp