Zack Weinberg wrote:
> $ diff -u m4/std-gnu11.m4{~,}
> --- m4/std-gnu11.m4~ 2020-08-30 11:27:01.000000000 -0400
> +++ m4/std-gnu11.m4 2020-12-20 09:43:13.001477099 -0500
> @@ -27,6 +27,8 @@
> # François Pinard, Karl Berry, Richard Pixley, Ian Lance Taylor,
> # Roland McGrath, Noah Friedman, david d zuhn, and many others.
>
> +m4_version_prereq([2.70], [], [
> +
>
> # AC_PROG_CC([COMPILER ...])
> # --------------------------
> @@ -822,3 +824,5 @@
> dnl with extended modes being tried first.
> [[-std=gnu++11 -std=c++11 -std=gnu++0x -std=c++0x
> -qlanglvl=extended0x -AA]], [$1], [$2])[]dnl
> ])# _AC_PROG_CXX_CXX11
> +
> +])# m4_version_prereq
>
> I recommend this patch be applied in Gnulib proper.
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 you can run
'./configure' right away.
If people want to modify the build infrastructure, it would often be
more reasonable to start off the git repository of the package (possibly
from a specific release tag or release branch).
Bruno
