Re: rm -f # no more args failure?

2021-12-12 Thread Mike Frysinger
On 12 Dec 2021 16:17, Karl Berry wrote: > Does anyone here use or know of an active system where plain > rm -f > with no arguments fails? I mean, exits with bad status? > > We are considering changing Automake to assume this works, > although we'd provide for a workaround just in case,

Re: [PATCH] configure: handle KCC on case-insensitive filesystems

2021-12-12 Thread Karl Berry
Subject: [PATCH] configure: handle KCC on case-insensitive filesystems Pushed with doc tweak per Jim. Thanks.

bug#21336: [PATCH] configure: handle KCC on case-insensitive filesystems

2021-12-12 Thread Karl Berry
Subject: [PATCH] configure: handle KCC on case-insensitive filesystems Pushed with doc tweak per Jim. Thanks.

Re: [PATCH] gitignore: update

2021-12-12 Thread Karl Berry
> +*~ > +.#* Suggest also adding \#*# (emacs autosave files) and .*.sw[op] (vim autosave files). Pushed, thanks.

Re: [PATCH] m4: replace AC_DIAGNOSE with m4_warn

2021-12-12 Thread Karl Berry
--- a/m4/obsolete.m4 +++ b/m4/obsolete.m4 Pushed, thanks. grep -r shows more occurrences of AC_DIAGNOSE in m4/init.m4 (seems straightforward) and mkdirp.m4, which seems to be a decision that was undone, but I don't have the energy to try to find the discussion now to see how to "adjust

Re: rm -f # no more args failure?

2021-12-12 Thread Bob Friesenhahn
On Sun, 12 Dec 2021, Karl Berry wrote: Does anyone here use or know of an active system where plain rm -f with no arguments fails? I mean, exits with bad status? I thought that systems deriving from OpenSolaris (e.g. Illumos, OpenIndiana, etc.) had that issue until ksh93 was fixed recently.

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

2021-12-12 Thread Karl Berry
> To help ease people into enabling silent rules by default, warn if FWIW, I don't agree with any of these silent-rule patches, for all the reasons Zack explained. They just seem like they are inflicting pain on existing users with no return benefit. -k

rm -f # no more args failure?

2021-12-12 Thread Karl Berry
Does anyone here use or know of an active system where plain rm -f with no arguments fails? I mean, exits with bad status? We are considering changing Automake to assume this works, although we'd provide for a workaround just in case, something like make RM_F="rm -f nosuchfile" But if there

bug#21336: [PATCH] configure: handle KCC on case-insensitive filesystems

2021-12-12 Thread Jim Meyering
On Thu, Dec 9, 2021 at 10:56 PM Mike Frysinger wrote: > This fixes https://debbugs.gnu.org/21336. On macOS 10.10, there seems Note that I still see kcc on 12.0.1 > to be a kerberos tool installed as "kcc" which breaks the check. > > Also resync with latest autoconf which searches for clang++

Re: [PATCH] configure: handle KCC on case-insensitive filesystems

2021-12-12 Thread Jim Meyering
On Thu, Dec 9, 2021 at 10:56 PM Mike Frysinger wrote: > This fixes https://debbugs.gnu.org/21336. On macOS 10.10, there seems Note that I still see kcc on 12.0.1 > to be a kerberos tool installed as "kcc" which breaks the check. > > Also resync with latest autoconf which searches for clang++

Re: [PATCH] m4: replace AC_DIAGNOSE with m4_warn

2021-12-12 Thread Jim Meyering
On Sat, Dec 11, 2021 at 10:07 PM Mike Frysinger wrote: > 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

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

2021-12-12 Thread Jim Meyering
On Sat, Dec 11, 2021 at 10:09 PM Mike Frysinger wrote: > 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(-) > >

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

2021-12-12 Thread Jim Meyering
On Sun, Dec 12, 2021 at 7:14 AM Zack Weinberg wrote: > > On Sun, Dec 12, 2021, at 1:10 AM, Mike Frysinger wrote: > > 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 >

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

2021-12-12 Thread Zack Weinberg
On Sun, Dec 12, 2021, at 1:09 AM, Mike Frysinger wrote: > To help ease people into enabling silent rules by default, warn if > a package doesn't make an explicit selection. -1 for the same reason that changing the default is a bad idea. If we are to make *any* change in this area I would

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

2021-12-12 Thread Zack Weinberg
On Sun, Dec 12, 2021, at 1:10 AM, Mike Frysinger wrote: > 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

Re: [PATCH] gitignore: update

2021-12-12 Thread Zack Weinberg
On Sun, Dec 12, 2021, at 1:07 AM, Mike Frysinger wrote: > Ignore all *~ files as editors like to create them, as do some > autotool steps. This also matches what autoconf is doing. ... > +*~ > +.#* Suggest also adding \#*# (emacs autosave files) and .*.sw[op] (vim autosave files). zw