[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: m4_foreach_w(...AC_DEFINE...) expansion change in 2.72e?
From: |
Zack Weinberg |
Subject: |
Re: m4_foreach_w(...AC_DEFINE...) expansion change in 2.72e? |
Date: |
Thu, 21 Dec 2023 15:45:03 -0500 |
User-agent: |
Cyrus-JMAP/3.9.0-alpha0-1364-ga51d5fd3b7-fm-20231219.001-ga51d5fd3 |
On Thu, Dec 21, 2023, at 2:39 PM, Paul Eggert wrote:
> I'm seeing the same bug with Autoconf 2.69 on RHEL 7. Tarball attached
> with the configure.ac that I used, and the output of "autoheader" and
> "autoconf".
Thanks for checking, Paul.
I see the same phenomenon with 2.71, I can't reproduce any difference
between 2.71 and 2.72 (dev trunk), and I can fix the generated
config.h.in and configure by making two changes: Unquote
"kpse_otftotfm_auto_opts" in the second foreach (the one that invokes
AC_DEFINE), and insert a newline immediately after the close parenthesis
of the AS_IF().
The second change is not necessary to make m4_foreach_w iterate, but it
*is* necessary to prevent the *result* of the iteration from running
each "fi" together with the next "if", causing shell syntax errors.
Optionally, also change AC_FOREACH to m4_foreach_w to fix the warning
about AC_FOREACH being obsolete.
Karl: you said that unquoting "kpse_otftotfm_auto_opts" did _not_ fix
the problem for you. Is it possible that there's some difference
between the complete Texlive configure script and the cut-down version
you posted, that's responsible for this?
zw