Re: [RFC/PATCH] m4: enable silent build rules by default

2021-12-11 Thread Mike Frysinger
On 07 Dec 2021 21:58, Zack Weinberg wrote: > On Tue, Dec 7, 2021, at 9:49 PM, Mike Frysinger wrote: > > This has been available since automake 1.11 released over a decade > > ago. Let's flip the default to enable silent builds by default. > > Please don't *ever* make this change. It is absolutel

[PATCH 2/2] m4: enable silent build rules by default

2021-12-11 Thread Mike Frysinger
This has been available since automake 1.11 released over a decade ago. Let's flip the default to enable silent builds by default. NB: The "1.20" version is a placeholder. With the warning for devs in 1.17, we can wait a while before rolling this out. --- NEWS | 9 + m4/silent.m

[PATCH 1/2] m4: warn when AM_SILENT_RULES default is used

2021-12-11 Thread Mike Frysinger
To help ease people into enabling silent rules by default, warn if a package doesn't make an explicit selection. --- NEWS | 10 ++ m4/silent.m4 | 6 +- 2 files changed, 15 insertions(+), 1 deletion(-) diff --git a/NEWS b/NEWS index fb05ee219708..282eb9277a3d 100644 --- a/NEWS

[PATCH] m4: replace AC_DIAGNOSE with m4_warn

2021-12-11 Thread Mike Frysinger
AC_DIAGNOSE was marked obsolete with autoconf-2.62 in 2008. * m4/obsolete.m4: Change AC_DIAGNOSE to m4_warn. --- m4/obsolete.m4 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/m4/obsolete.m4 b/m4/obsolete.m4 index 79f3b234bfc5..bf3b68271673 100644 --- a/m4/obsolete.m4 +++

[PATCH] gitignore: update

2021-12-11 Thread Mike Frysinger
Ignore all *~ files as editors like to create them, as do some autotool steps. This also matches what autoconf is doing. * .gitignore: Update. --- .gitignore | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.gitignore b/.gitignore index 89e71ec97d5a..22f40fe9f51f 100644 ---

Re: [RFC/PATCH] m4: enable silent build rules by default

2021-12-11 Thread Mike Frysinger
On 08 Dec 2021 15:02, Karl Berry wrote: > Please don't *ever* make this change. > > I agree with Zack, and just for CI purposes; it is simply too big of an > incompatibility to inflict at this late date. there's nothing incompatible about it. the inputs to the system (how configure & make ar