>there's no good reason for autoconf to start poaching on symbols that
>don't begin with AC_. File it as a bug in autoconf.
Recent versions of autoconf appear to split a lot of the autconf
functionality between autoconf proper and "m4 sugar." I think the
idea is that the m4sugar code could be useful for other things, so
that why I think they want a second prefix. Personally, I think
that second prefix should be something less likely to collide with
existing variable (like M4S_, say), and that autoconf should just
generate warning about this since it does not know what variables
people have used up to this point.
In general, I think a number of recent changes in autoconf
have broken backward compatability unnecessarily.
Nevertheless, autoconf-2.53 is out there. You will probably
have to field the same trouble report repeatedly if you do not work
around the problem. The workaround is not only very simple; it's also
an improvement. ASM_xxxxxxx is more mnemonic than AS_xxxxx and more
consistent with other flags related to assember issues in gcc. So, I
would still recommend that you apply my patch.
Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104
[EMAIL PROTECTED] \ / San Jose, California 95129-1034
+1 408 261-6630 | g g d r a s i l United States of America
fax +1 408 261-6631 "Free Software For The Rest Of Us."
