Re: [2.63] - problem parsing generated configure or config.status

[Ralf Wildenhues]

Hello Borg,

* Unknown wrote on Mon, Jun 22, 2009 at 11:34:26PM CEST:
> I have problem w/ newest autoconf-2.63 generated files.
> This is how it looks in case of git-1.6.3.3 (recently they moved from
> 2.61 to 2.63):

Hmm, I don't see the v1.6.3.3 tag in the git git tree; but surely the
file is on the web server.

> configure: creating ./config.status
> ./config.status: line 666: syntax error near unexpected token `;'
> ./config.status: line 666: `   { (exit 1); exit 1; }; };;'
> 
> line 666:    { (exit 1); exit 1; }; };;

I see this construct in the generated config.status file, but I can't
see anything wrong with it (the final ;; ends a case statement).  I'm
afraid you might have to debug it yourself, as I don't have any systems
currently running with bash 2.05b installed any more, and I've confirmed
your observation that it doesn't hit with a self-compiled 2.05 on
GNU/Linux.  This shell is 7 years old and Cygwin is easily updated, why
not move to a newer version?

That said, if you can analyze the issue and we find an easy workaround,
we can still consider it.

Thanks for the report,
Ralf