On Sun, Jul 06, 2025 at 09:09:53PM +0800, Yuao Ma wrote: > Hi Tobias, > > On 7/6/2025 6:34 PM, Tobias Burnus wrote: > > As that commit is from 2020 and 2.69 in from 2012, it seems as if your > > autoconf is too new. Can you re-check that the right version is at the > > beginning of the PATH? > > > > Note that there is a CI job that checks whether the generated files are > > in deed up to date, i.e. the current trunk should be fine unless someone > > has messed up. > > > > It is possible that autoconf 2.69 contains this commit, as we can see from > https://github.com/autotools-mirror/autoconf/commit/a1d8293f3bfa2516f9a0424e3a6e63c2f8e93c6e > that it has been backported to v2.69b - v2.69e. > > The main reason is that my devbox has autoconf2.69 (2.69-3.1) from Debian, > released on Sat, 19 Nov 2022 21:40:11 +0200, which includes the commit from > 2020. This version takes precedence over my compiled version. Once I switch > to my compiled version, the generation output functions as expected. > > > The other question is whether the autoconf version shouldn't be updated, > > given that 2.69 is quite old. > > Upgrading this basic component may seem like a major change, but opting for > the same version with a backported patch appears to be a better choice. >
Please see https://gcc.gnu.org/install/prerequisites.html. That page specifically says "autoconf version 2.69"; not some 2.69-patch-level. Everyone using the same release prevents conflicting changes. -- steve
