Re: [PATCH] [4/14] Completes renaming of configure.in files to .ac

["H.J. Lu" <hjl dot tools at gmail dot com>]

On Thu, Jul 16, 2015 at 8:09 PM, Michael Darling <darlingm@gmail.com> wrote:
> (I was requested by binutils to split my May 24 and Jul 16 patches
> into separate files for each binutils-gdb main subdirectory.)
>
> Combined builds has been broken for about 10 months, because some binutils
> configure.in files were renamed to configure.ac, but gcc's references to them
> were not updated.  Fixing gcc's references to them is much easier by renaming
> the few straggling configure.in files to configure.ac. gcc's configure.in
> files were entirely renamed to configure.ac some time ago. There are
> corresponding patches submitted to gcc, which updates all references to
> binutils-gdb configure.in files to configure.ac, which is what ultimately
> fixes combined builds.
>
> See PR binutils-gdb/binutils/18450 and gcc/other/66259.
>
> Signed-off by: Michael Darling <darlingm@gmail.com>
> ---
>  config/ChangeLog  | 8 ++++++++
>  config/gettext.m4 | 4 ++--
>  config/po.m4      | 4 ++--
>  config/stdint.m4  | 2 +-
>  config/tcl.m4     | 4 ++--
>  5 files changed, 15 insertions(+), 7 deletions(-)

Since all configure files are generated from them, this patch must be
checked in first.
But some of them are imported and some imported packages still use configure.in,
not configure.ac.

What is the real value of changing "configure.in" in comments/messages to
"configure.ac" when both are used in packages?

-- 
H.J.