[RFC PATCH 0/3] kbuild: In quiet mode, print the full command line if it fails

[Ben Hutchings <ben@decadent.org.uk>]

[-- Attachment #1: Type: text/plain, Size: 1277 bytes --]

The default (quiet) kbuild output is usually preferable to a log
showing every command line in full.  However, after a failure the
full command line may be more interesting.  When building from an
interactive shell, it's trivial to retry the build with V=1, but in
case the failed build was automated this is not so easy.

For example,
<https://buildd.debian.org/status/fetch.php?pkg=linux&arch=powerpcspe&ver=4.18%7Erc4-1%7Eexp1&stamp=1531410477&raw=0>
is a build failure triggered by a change in the default compiler
options for powerpc.  This failure is from a native build and I
cannot reproduce it in a cross-build environment.  From the quiet
build log I can't tell whether the same compiler options were used
in the native build.

This series changes the various standard macros used to run and
(depending on verbosity) echo a command.  In quiet mode, if a
command fails it will be echoed before exiting the shell.

Ben.

Ben Hutchings (3):
  kbuild: Move final argument to modpost into $(cmd_modpost)
  kbuild: Add $(run-cmd) macro for running and maybe echoing command
  kbuild: In quiet mode, print the full command line if it fails

 scripts/Kbuild.include   | 13 +++++++++----
 scripts/Makefile.modpost |  4 ++--
 2 files changed, 11 insertions(+), 6 deletions(-)


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]