Re: undefined macro

[Ralf Wildenhues]

Hello Ben,

* address@hidden wrote on Thu, Mar 29, 2007 at 05:37:20AM CEST:
> 
> Jason kindly gave me a login on the system that was exhibiting
> the problem.  I think I tracked down the problem.  My analysis
> follows.

I'm sorry that you had to do it for this known bug.  I guess I should
have written more clearly in my earlier response.

> Conclusions:
> 
> 1. Jason: I think you can fix the problem by upgrading to the
>    latest version of GNU m4.

ACK.

> 2. I don't understand why m4 behavior changed.  It doesn't seem
>    to be mentioned explicitly anywhere in NEWS.  I guess it must
>    be related to this item for version 1.4.4b, though:

Yes.

> 3. It seems that Autoconf should more strongly recommend, or even
>    test for and require, a recent version of m4, since older
>    versions can cause such bizarre, difficult-to-debug problems.

Yes, in response to a couple of reports about this bug, CVS Autoconf 
now has this NEWS entry:

| ** Autoconf now requires GNU M4 1.4.5 or later.  Earlier versions of M4 have
|    a bug in macro tracing that interferes with the interaction between
|    Autoconf and Automake.  GNU M4 1.4.8 or later is recommended.

Apologies for any miscommunication I was part of.

Cheers,
Ralf