[sr #111138] precise error message "possibly undefined macro: ..."

--8323329-1649760492-1769539634=:3173766
Content-Type: TEXT/plain; CHARSET=utf-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-Disposition: inline

Update of sr #111138 (group autoconf):=0A=0A                Priority:      =
 5 - Unprioritized =3D> 2 - Eventually=0A                  Status:         =
           None =3D> Confirmed=0A=0A    ___________________________________=
____________________=0A=0AFollow-up Comment #3:=0A=0AHmm, fundamentally I t=
hink what you're asking for is for us to add AX_ to the=0Aset of word prefi=
xes that trigger "possibly undefined macro" diagnostics when=0Athey appear =
in the generated configure script.  That doesn't seem crazy to me=0Aoff the=
 top of my head, but I am not going to make that change in a hurry=0Aprior =
to a release that's supposed to be a very safe upgrade to fix a few=0Acriti=
cal bugs.  I'd also like to hear what other people think of the idea=0Afirs=
t.=0A=0AAlso, I think it's quite likely that improper M4 quotation is contr=
ibuting to=0Athe problem you're seeing.  It probably won't be possible to m=
ake autoconf=0A_stop_ complaining about "possibly undefined macro: AC_SUBST=
".  It'd help me=0Aunderstand why that happened if you sent in a _complete_=
 but also _minimized_=0Atest case that produces that error message.=0A=0A=
=0A    _______________________________________________________=0A=0AReply t=
o this item at:=0A=0A  <https://savannah.gnu.org/support/?111138>=0A=0A____=
___________________________________________=0AMessage sent via Savannah=0Ah=
ttps://savannah.gnu.org/=0A
--8323329-1649760492-1769539634=:3173766
Content-Type: APPLICATION/pgp-signature; name=signature.asc

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQQk97aszIMMAvLLwm6qLAuaBUf3TgUCaXkIMgAKCRCqLAuaBUf3
TjE6AP9wdmryQ4yiFt0LABPrIf1zBxNSPo2MxCyp9G5hXGub7wD/ZQdNoE+62NYK
aVea7VURi/sI4ny+77SUvmqdtr+wzwY=
=6bdM
-----END PGP SIGNATURE-----

--8323329-1649760492-1769539634=:3173766--