aboutsummaryrefslogtreecommitdiff
path: root/gdb/target-delegates.c
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2024-04-05 09:56:32 +0100
committerAndrew Burgess <aburgess@redhat.com>2024-04-08 10:25:37 +0100
commitcc7ae3ac7e7e07b3fb8e6050bd728b466e6410e4 (patch)
tree8d72f2b2617adcd526bd50a807c0fe4e25a9f25a /gdb/target-delegates.c
parentecc3c386677c2c096b2d589588dd26d21a0fb476 (diff)
downloadgdb-cc7ae3ac7e7e07b3fb8e6050bd728b466e6410e4.zip
gdb-cc7ae3ac7e7e07b3fb8e6050bd728b466e6410e4.tar.gz
gdb-cc7ae3ac7e7e07b3fb8e6050bd728b466e6410e4.tar.bz2
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>
Diffstat (limited to 'gdb/target-delegates.c')
0 files changed, 0 insertions, 0 deletions