https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400

--- Comment #8 from kargls at comcast dot net ---
On 5/27/25 15:04, iains at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=116400
> 
> --- Comment #6 from Iain Sandoe <iains at gcc dot gnu.org> ---
> (In reply to kargls from comment #4)
>> FX, Iain,
>>
>> Can one of you please fix this bug or revert your patch?
> 
> It would be unfortunate to return to the situation where we cannot use
> autoreconf to regenerate the Fortran configurations.
>

Tracked down some info:

    https://gcc.gnu.org/pipermail/fortran/2024-April/060439.html

    @tschwinge since he did quite a bit of work on getting autoreconf to
    work in the GCC-13 cycle.

    This does not address the issues with regenerating lib code, but it
    does make things somewhat smoother for cases where the updates are
    only in Makefile.am, configure.ac or libtool.m4 for example.

This suggests that it was known that the patch broke (re)generation
of library code, but it was committed anyway.  Testing seems to support
this.

% cd gcc/gccx
% git status libgfortran/m4/spread.m4
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
   (use "git add <file>..." to update what will be committed)
   (use "git restore <file>..." to discard changes in working directory)
         modified:   libgfortran/m4/spread.m4
Untracked files:
   (use "git add <file>..." to include in what will be committed)
         pr77415.txt

no changes added to commit (use "git add" and/or "git commit -a")
% autoreconf -vf libgfortran
autoreconf: Entering directory `libgfortran'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force -I .. -I ../config
autoreconf: configure.ac: tracing
autoreconf: configure.ac: not running libtoolize: --install not given
autoreconf: running: /home/kargl/work/bin/autoconf --force
autoreconf: running: /home/kargl/work/bin/autoheader --force
autoreconf: running: automake --force-missing
autoreconf: Leaving directory `libgfortran'
% git status
On branch master
Your branch is up to date with 'origin/master'.

Changes not staged for commit:
   (use "git add <file>..." to update what will be committed)
   (use "git restore <file>..." to discard changes in working directory)
         modified:   libgfortran/m4/spread.m4
...

Reply via email to