[binutils-gdb] gdb/Makefile: add gcore to the 'all' target dependency list

[binutils-gdb] gdb/Makefile: add gcore to the 'all' target dependency list

[Andrew Burgess]

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=cc7ae3ac7e7e07b3fb8e6050bd728b466e6410e4

commit cc7ae3ac7e7e07b3fb8e6050bd728b466e6410e4
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Fri Apr 5 09:56:32 2024 +0100

    gdb/Makefile: add gcore to the 'all' target dependency list
    
    The gcore script is initially generated by the configure process, just
    like gdb-gdb.gdb and gdb-gdb.py.  However if the gdb/gcore.in input
    source is modified then 'make all' in the gdb/ directory does not
    regenerate the gcore script.
    
    This is different than the gdb-gdb.gdb and gdb-gdb.py files, if their
    input is updated then 'make all' will regenerate these files.
    
    The difference is that for gdb-gdb.* there is an explicit dependency
    between the 'all' target and the generated file, this dependency is
    missing for gcore.
    
    This commit adds the dependency.  Now, if gcore.in is changed, running
    'make all' will regenerate the gcore script.
    
    There is no change in _what_ is generated after this commit.
    
    Approved-By: Simon Marchi <simon.marchi@efficios.com>

Diff:
---
 gdb/Makefile.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gdb/Makefile.in b/gdb/Makefile.in
index a9f641c0659..df044288b5e 100644
--- a/gdb/Makefile.in
+++ b/gdb/Makefile.in
@@ -1938,7 +1938,7 @@ generated_files = \
 # Flags needed to compile Python code
 PYTHON_CFLAGS = @PYTHON_CFLAGS@
 
-all: gdb$(EXEEXT) $(CONFIG_ALL) gdb-gdb.py gdb-gdb.gdb
+all: gdb$(EXEEXT) $(CONFIG_ALL) gdb-gdb.py gdb-gdb.gdb gcore
 	@$(MAKE) $(FLAGS_TO_PASS) DO=all "DODIRS=$(SUBDIRS)" subdir_do
 
 # Rule for compiling .c files in the top-level gdb directory.