[PATCH 1/4] Regenerate GNU Autotools files

[Nick Clifton]

Hi Tulio,

>> More to the point however
>> is are we going to insist that the CentOS-9 versions of the tools
>> be used for all future regenerations ?
> 
> That's indeed my proposal. I believe that sticking to a free, LTS/stable
> distro would help us to rerun autoreconf from a container easily. 

Why are you running autoreconf in a container ?

Is this because you have installed the sources and are now trying to build
the annobin binaries ?  If this is the case then wouldn't it be easier to
simply stop autoreconf from running ?  For example the annobin.spec file
for all Fedora, CentOS and RHEL releases contains this fragment of code:

   # The plugin has to be configured with the same arcane configure
   # scripts used by gcc.  Hence we must not allow the Fedora build
   # system to regenerate any of the configure files.
   touch aclocal.m4 gcc-plugin/config.h.in
   touch configure */configure Makefile.in */Makefile.in
   # Similarly we do not want to rebuild the documentation.
   touch doc/annobin.info

If we are going require specific tool versions, how will we enforce this
requirement ?  (And also where will we document it ?)

I think that I am correct in saying that if I run autoreconf it will
use whichever versions of the tools appear first in my search PATH.  So
presumably I will have to make sure that I have the correct versions
ahead of any system versions.  (Unless I happen to be developing on a
CentOS-9 box).

> It doesn't have to be c9s, though.

Yeah, I do not mind which standard set we choose.

Cheers
   Nick