The user still has full control over verbosity levels, both setting
their per-project defaults at configure time (or even in a config.site
file), as well as a per-run override. But these days, most projects
are defaulting to silent rules without user intervention.
* configure.ac (AM_SILENT_RULES): Add, to match what most projects
are doing these days.
Signed-off-by: Eric Blake <eblake@redhat.com>
(cherry picked from commit
b4a08ecfd34e703bd846f1e85b4e2a94a34b16d9)
[For the cherry-pick, all we have to do is normalize the spelling
of the line - now that we require new-enough automake, it does not
have to be conditional]
index 16aa393df76de7943305fdfb474c3a075b6a6e8d..c4644af5b11042d22cde391ed561245df8e73a3c 100644 (file)
@@ -57,7 +57,7 @@ M4_default_preload="M4_DEFAULT_PRELOAD"
AM_INIT_AUTOMAKE([1.11.6 subdir-objects dist-bzip2 dist-xz
color-tests parallel-tests silent-rules]
m4_if(m4_index(m4_defn([M4_VERSION]), [-]), [-1], [gnits], [gnu]))
-m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])])
+AM_SILENT_RULES([yes]) # make --enable-silent-rules the default.
## ------------------ ##