Follow-up Comment #2, sr #110350 (project autoconf): > is maintaining compatibility the sticking point, or is it that you want a better API to enable what AX_PROC_CC_FOR_BUILD did?
Right now we want to maintain compatibility. Developing a better API and fixing the problem within ax_prog_cc_for_build.m4 would both take too long for the 2.70 release timeframe. > how important is it to use AC_DEFUN_ONCE for AC_PROG_CC? I honestly don't know. The change was made eight years ago with very little rationale - see https://lists.gnu.org/archive/html/autoconf-patches/2012-09/msg00034.html , which was committed nearly verbatim. It would be simple enough to revert that change, but I would want to write tests to ensure this doesn't break again (at least not until we do have a better API) and it might make sense to try to accomplish the goal of the change - reducing the size of a generated configure script - some other way (e.g. factoring out as much as possible of the code emitted by AC_PROG_CC to a shell function). _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/support/?110350> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
