Michael Elizabeth Chastain writes:
> eza> [PS. I assume I used the correct autoconf, but I am nost sure: I used the
> eza> autoconf-000227 snapshot].
>
> ms> In view of the large diffs in configure, I suspect this is indeed the
> ms> wrong version of autoconf. The rest of the change is approved. If you
> ms> don't easily solve the autoconf issue, you might consider leaving
> ms> configure alone -- it's just an extra test...
>
> A little sniffing indicates that the last commit to 'configure.in'
> used autoconf 2.13 to generate 'configure'. That's where the diff
> is coming from.
I think that 000227 also brands itself as 2.13. I think this may be
where the confusion comes from, the configure file tells you
"configure generated by autoconf version 2.13" in both cases.
>
> So either the blessed version has changed, or the last commit to
> 'configure.in' was done with the wrong autoconf.
>
> I agree it might be useful to split the patch, if we can't get a
> quick resolution to "which autoconf is blessed".
>
Ok, this issue seems to be resolved now. Let me know when I can commit,
or not :-).