Re: autoconf 2.72/2.73

[Frederic Berat]

On Mon, Apr 3, 2023 at 9:19 AM Paul Eggert <eggert@cs.ucla.edu> wrote:
>
> On 2023-04-03 00:08, Frederic Berat wrote:
>
> > The build is done from an RCS tarball, but auroconf/autoreconf is
> > called. Which leads to failure:
>
> Yes, I think that agrees with what I said. As I understand it:

I mentioned it only for completeness.

>
> If you take the latest RCS and run 'configure; make' it works.
>
> If you take the latest RCS release and run 'autoconf;configure;make'
> with released Autoconf, it works.
>
> If you take the latest RCS release, update its .m4 file with
> bleeding-edge Gnulib, and then run 'autoconf;configure;make' with
> bleeding-edge Autoconf, it works.
>
> If you take bleeding edge Autoconf from Savannah Git, use bleeding-edge
> Autoconf, it works.
>
> If you take the latest RCS release, but do not update its .m4 file with
> bleeding-edge Gnulib, and then run 'autoconf;configure;make' with
> bleeding-edge Autoconf anyway, it doesn't work. So don't do that; do one
> of the other things.
>

Thanks for the details.

It would have been nice to keep these macro around for backward
compatibility. Assuming they are only used by gnulib, they wouldn't
need to be kept for too long.