Re: wish list

[Paolo Bonzini]

> - the new AC_REQUIRE warnings may not be easy to solve in general.
> Consider the following situation: you require two macros, both from
> different third parties (a third and a fourth party?).  One requires
> a common macro, say AC_PROG_CC, another expands it.

I think that would be a bug in the macro expanding it.

> You cannot easily
> solve this situation.  It might be a bug, but then again, it doesn't
> have to be: it can depend upon the semantics of the common macro
> whether this is a problem.  Sometimes multiple invocation is actually
> intended, be that because the configure.ac author plays tricks with
> unset, shell flow of execution constructs (loops, branches), etc.

Yes, that's why for example AC_PROG_CC was not changed to AC_DEFUN_ONCE.

Paolo