Re: autoreconf on msys2@Windows10 does not regenerate the configure script

[Thomas Dickey]

On Sun, Oct 11, 2020 at 09:10:13PM +0200, Anonymous Maarten wrote:
> Hello,
> 
> Autoconf 2.52 (fetched from invisible-island.net
> <https://invisible-island.net/datafiles/release/autoconf.tar.gz>) on
> msys2@Windows 10
> does not regenerate the configure script completely the same and correctly.
> The changes result in a non-functional configure script.
> Running the regenerated ncurses ./configure results in the following error:
> 
> > configure: creating ./config.status
> > ./config.status: line 273: syntax error near unexpected token `\"'
> > ./config.status: line 273: `  "\" ) CONFIG_FILES="$CONFIG_FILES \" ;;'
> >
> 
> I think running autoreconf on an untouched master should not modify the
> configure script, shouldn't it?

As a general rule, I don't use autoreconf (the Xorg projects on gitlab
are an exception to that rule).  autoreconf is used mainly to work around
a discordance between autoconf and automake(*).  Since ncurses doesn't use
automake, I don't have to solve problems created by automake.

When I generate the configure script, all I do is run "autoconf"
(I install it as "autoconf-252").

(*) autoreconf predates automake, originally used in a role like autoheader.
    One of my users suggested that it would be nice if I make the macros
    work with autoheader; I do fixes for that occasionally.  But I haven't
    found a use for autoreconf.
 
-- 
Thomas E. Dickey <dickey@invisible-island.net>
https://invisible-island.net
ftp://ftp.invisible-island.net

signature.asc
Description: PGP signature