Regenerating preconfigure files

[Mark Wielaard]

Hi,

On Sun, Aug 24, 2025 at 11:39:46PM +0200, Mark Wielaard wrote:
> 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.

This seems to work well and doesn't take much time (a couple of
minutes at most). It hasn't caught any issues yet (in the last ~80
commits), but in case it will in the future I added a reporter that
will sent email to the patch author and the libc-testresults list.

Cheers,

Mark