Follow-up Comment #3, sr #110399 (project autoconf):
When a longstanding core existing feature (AC_PROG_CC) is changed in a
backward-incompatible way, a way to get the heretofore standard behavior feels
more like a bug fix than a feature request to me. For that matter, it feels
like a new macro or option would have been more desirable than incompatibly
changing existing behavior.
Anyway. Semantics aside, I had the same reaction to the weird error about
"long int". I haven't had a chance to look into it yet, but my expectation is
that it is something specific to the TL autoconfigury. (I mean, presumably
int64_t should not be getting #define-d in the first place.) I've been using
Autoconf for TeX since Autoconf first existed, and never had to change most of
it. So I won't be surprised that something is going awry now.
If something is actually going wrong on the Autoconf side, I'll post a
separate report.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?110399>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
