aboutsummaryrefslogtreecommitdiff
path: root/gdb/opencl-lang.c
diff options
context:
space:
mode:
authorAndrew Burgess <aburgess@redhat.com>2024-04-05 10:53:00 +0100
committerAndrew Burgess <aburgess@redhat.com>2024-04-08 10:25:40 +0100
commitb6a12c14513f1c46a74a78eebe0e57a7e3c93846 (patch)
tree2a4ef8a4273b4a4fa31e66495c0f0fec24af1cea /gdb/opencl-lang.c
parentcb1bef582e37d29281a5a5ebd99605d55afb16a0 (diff)
downloadgdb-b6a12c14513f1c46a74a78eebe0e57a7e3c93846.zip
gdb-b6a12c14513f1c46a74a78eebe0e57a7e3c93846.tar.gz
gdb-b6a12c14513f1c46a74a78eebe0e57a7e3c93846.tar.bz2
gdb/Makefile: Print 'GEN' message, and pass SILENT_FLAG more
The targets that use config.status to regenerate themselves don't currently follow the silent rules that the rest of GDB's Makefile does. For example, touch the gdb/gcore.in file and then 'make all' in the gdb/ directory prints: /bin/sh config.status gcore config.status: creating gcore In this commit I make use of the silent-rules.mk mechanism for these targets, now we get: GEN gcore Which matches the rest of our Makefile. Obviously, if you pass 'V=1' to the build then you'll get the old output back. There's no change in what is generated after this commit. Approved-By: Simon Marchi <simon.marchi@efficios.com>
Diffstat (limited to 'gdb/opencl-lang.c')
0 files changed, 0 insertions, 0 deletions