Regenerating preconfigure files

[Mark Wielaard]

Hi,

On Sun, Aug 24, 2025 at 01:14:40AM +0200, Mark Wielaard wrote:
> On Tue, Aug 19, 2025 at 10:12:11AM +0200, Andreas K. Huettel wrote:
> > In our documentation, 
> > https://sourceware.org/glibc/wiki/Regeneration
> > autoconf regeneration is only applied to literal 'configure.ac' files. 
> > 
> > Should this be extended to *configure.ac files, so it includes the
> > preconfigure.ac fragments?
> >
> > See e.g. d4cdb601df0a125550341f85d7011314e4746308 which would have
> > been caught by this automatically during release process.
> 
> Some other projects have autoregen buildbots that run after each
> commit to check all files have been correctly regenerated.
> 
> https://builder.sourceware.org/buildbot/#/builders/gcc-autoregen
> https://builder.sourceware.org/buildbot/#/builders/binutils-gdb-autoregen
> 
> It occassionally finds issues. We should have the same for glibc so
> badly or forgotten regenerated files are detected early (makes for
> less work for the release manager).

I created one for glibc:
https://sourceware.org/cgit/builder/commit/?id=499e75a3eb6b32aa01f1646b1033876f863a0470
https://builder.sourceware.org/buildbot/#/builders/glibc-autoregen

At the moment it just regenerates the autoconf [pre]configure scripts,
the locale/programs/*-kw.h files and the INSTALL file and checks the
version checked in is the same.

It doesn't regenerate the Unicode files (but does contain the code to
do it) because those have an embedded generation time stamp so are
always different (but only the date is). It would probably be good to
remove those timestamps to make them reproducible.

There is a note on the wiki about regenerating C-translit.h. But since:

commit 053c52b17739a584ee73d336e547b15abcdabd49
Author: Florian Weimer <fweimer@redhat.com>
Date:   Tue Dec 18 11:36:29 2018 +0100

    locale: Rewrite locale/gen-translit.pl in Python

This file is not checked into git, but just always generated in the
build dir. I have removed it from the wiki page.
 
Where would be a good place to report failures?

Cheers,

Mark