[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: autoconf 2.72/2.73
|
From: |
Paul Eggert |
|
Subject: |
Re: autoconf 2.72/2.73 |
|
Date: |
Mon, 3 Apr 2023 00:19:33 -0700 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 |
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:
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.