Re: Reautoconfing

2020-12-20 Thread Wookey
On 2020-12-20 13:37 -0800, Paul Eggert wrote: > On 12/20/20 12:25 PM, Wookey wrote: > > We realise that it was/is not the autotools design, but that design > > only works well when the auto* bits get updated reasonably often. > > Yes, the design assumes that Autoconf etc. are maintained well,

Re: Reautoconfing

2020-12-20 Thread Paul Eggert
On 12/20/20 12:25 PM, Wookey wrote: We realise that it was/is not the autotools design, but that design only works well when the auto* bits get updated reasonably often. Yes, the design assumes that Autoconf etc. are maintained well, which (except for Zack's efforts) has not been the case for

Re: Reautoconfing

2020-12-20 Thread Wookey
On 2020-12-20 17:46 +0100, Bruno Haible wrote: > This patch is already in Gnulib since 2020-12-09. But when people > run 'autoreconf' on an existing released tarball, they are effectively > combining an older Gnulib with a newest Autoconf. > > Why do people do that? The point of tarballs is that

Re: Request to revert the C version change

2020-12-20 Thread Zack Weinberg
On Sun, Dec 20, 2020 at 12:09 PM Zack Weinberg wrote: > I'm not happy about needing to kludge backward compatibility with the > older std-gnu11.m4 into autoconf 2.70.1 but I'm going to do it. It occurs to me that this would be less of a problem in the future if aclocal/autoreconf could update

Re: Request to revert the C version change

2020-12-20 Thread Zack Weinberg
On Sun, Dec 20, 2020 at 11:54 AM Ross Burton wrote: > On Sun, 20 Dec 2020 at 16:46, Bruno Haible wrote: >> This patch is already in Gnulib since 2020-12-09. But when people >> run 'autoreconf' on an existing released tarball, they are effectively >> combining an older Gnulib with a newest

Re: Request to revert the C version change

2020-12-20 Thread Zack Weinberg
On Sun, Dec 20, 2020 at 11:46 AM Bruno Haible wrote: > > Zack Weinberg wrote: > > $ diff -u m4/std-gnu11.m4{~,} > > --- m4/std-gnu11.m4~2020-08-30 11:27:01.0 -0400 > > +++ m4/std-gnu11.m42020-12-20 09:43:13.001477099 -0500 > > @@ -27,6 +27,8 @@ > > # François Pinard, Karl Berry,

Re: Request to revert the C version change

2020-12-20 Thread Ross Burton
On Sun, 20 Dec 2020 at 16:46, Bruno Haible wrote: > This patch is already in Gnulib since 2020-12-09. But when people > run 'autoreconf' on an existing released tarball, they are effectively > combining an older Gnulib with a newest Autoconf. > > Why do people do that? The point of tarballs is

Re: Request to revert the C version change

2020-12-20 Thread Bruno Haible
Zack Weinberg wrote: > $ diff -u m4/std-gnu11.m4{~,} > --- m4/std-gnu11.m4~2020-08-30 11:27:01.0 -0400 > +++ m4/std-gnu11.m42020-12-20 09:43:13.001477099 -0500 > @@ -27,6 +27,8 @@ > # François Pinard, Karl Berry, Richard Pixley, Ian Lance Taylor, > # Roland McGrath, Noah

Re: Request to revert the C version change

2020-12-20 Thread Zack Weinberg
On Wed, Dec 16, 2020 at 4:55 PM Todd C. Miller wrote: > > ./config.status: line 556: syntax error at line 562: `<<' unmatched Could you please clarify exactly which program's configure script gave this error? zw

Re: Request to revert the C version change

2020-12-20 Thread Zack Weinberg
On Wed, Dec 16, 2020 at 2:02 PM Zack Weinberg wrote: > On Wed, Dec 16, 2020 at 1:52 PM Ross Burton wrote: > > | checking for gcc option to enable C11 features... none needed > > | ../bison-3.7.4/configure: line 6187: syntax error near unexpected > > token `ac_cv_prog_cc_stdc=$ac_cv_prog_cc_c89'