https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400
--- Comment #9 from Iain Sandoe <iains at gcc dot gnu.org> --- If the Fortran maintainers prefer to revert the patch then I shall not complain. The configure version was changed in GCC-9 and no-one had stepped forward to update the Fortran build code even by GCC-15. I (and others) had also wasted time when reconfigure errors were missed in the pages of warnings coming from the unconverted code. That wasted time was my motivation to do the work for the patch. your recollection is, I think, correct, that the original change to autoconf-2.69 and automake-15.1 was committed knowing that libgfortran was unconverted. the patch was not committed knowing that this aspect was broken - it was committed without testing this aspect (arguably as bad, but...) I will try and look after 13.4 release work is out of the way. It would be much nicer if we could do something more like other places in the compiler, where there is some script to run in the source directory that can be done when one changes the m4 (and independently of the build).
