diff options
| author | Paul Eggert <eggert@cs.ucla.edu> | 2021-12-20 15:03:33 -0800 |
|---|---|---|
| committer | Paul Eggert <eggert@cs.ucla.edu> | 2021-12-20 15:05:08 -0800 |
| commit | aa1fdb3f6fe08169143a3062ca257be487713531 (patch) | |
| tree | 78d43013ba842ced374f96d7cd10600eb6f28339 /src/xterm.c | |
| parent | 5f57b41aa612e5f190f5a3c1ea013be114493a03 (diff) | |
| download | emacs-aa1fdb3f6fe08169143a3062ca257be487713531.tar.gz | |
Put AM_V_GEN etc. first
With the recent changes to src/verbose.mk.in, it’s more important
to be consistent about putting AM_V_GEN and similar macros at the
start of a rule’s recipe, since ‘make’ now outputs the diagnostic
before it executes the recipe rather than the shell outputting it.
Most of the uses were already this way, but there were a few
outliers. Problem reported by Pip Cet.
* Makefile.in (${srcdir}/info/dir):
* admin/unidata/Makefile.in (${unidir}/charprop.el, ${unifiles})
(${unidir}/emoji-labels.el):
* lib/Makefile.in (libgnu.a, libegnu.a):
* lisp/Makefile.in (TAGS):
* src/Makefile.in (lisp.mk, Emacs):
* test/Makefile.in (%.log, $(test_module)):
Put AM_V_GEN and similar macros first.
Diffstat (limited to 'src/xterm.c')
0 files changed, 0 insertions, 0 deletions