Re: Patch: gcc-3.0.4 workaround for AS_SPARC64_FLAG/autoconf-2.53

[Peter Eisentraut]

Dan Kegel writes:

> Also, I'm pretty sure I've seen projects using macros that start
> with AC_ (orbit has one, I think).  Maybe they do this for macros
> they want to propose for inclusion in autoconf.  Will autoconf
> choke on these, too?

You're missing the point.  The reason for this check is to catch calls to
undefined macros.  If a string refers to an undefined macro then m4 won't
expand it and it will stay in the configure output.  In the case under
consideration, autoconf thinks that AS_SPARC64_FLAG is a mistyped AS_*
macro.  There is nothing wrong with defining macros starting with AC_, as
long as they *are* defined.

-- 
Peter Eisentraut   address@hidden