Eric Gallager via Gcc <[email protected]> writes: > On Thu, Nov 5, 2026 at 12:02 PM Pietro Monteiro via Gcc <[email protected]> > wrote: >> >> I decided to try upgrading autoconf and automake to the latest >> available versions, respectively 2.73 and 1.19. I put the result in a >> branch on the forge (https://forge.sourceware.org/pietro/gcc.git >> branch upgrade-autotools) and I'm doing some basic testing. The patch >> at the tip of that branch depends on some patches I've sent >> recently[1,2,3] and a patch I haven't sent yet hat does the same as >> patch [3] but for libiberty. >> >> Before I go any further on this and start looking into upgrading >> binutils-gdb tree too I wanted to ask: >> >> 1) Is this something we want to do at this moment in the release cycle? >> >> 2) If so, are the versions I picked ok? I was told developers install >> autotools from source to avoid distro patches, so I went for latest. >> > > There is a bug with autoconf 2.73 that I would like to see fixed > before upgrading: https://savannah.gnu.org/support/?111401 > (Note that Savannah has been throwing 502 Bad Gateway errors on me > lately, so I can't confirm the latest status of it at the moment)
We can supply our own macros to do that if required, as we've done before. I'd prefer not to wait for it to be fixed upstream, as autoconf releases take years, we're already quite behind, and this blocks some further speedups too. sam
signature.asc
Description: PGP signature
