[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: popdef(undefined), __m4_version__

From: Eric Blake
Subject: Re: popdef(undefined), __m4_version__
Date: Mon, 21 Jul 2008 22:27:35 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

Eric Blake <ebb9 <at> byu.net> writes:

> > +/home/ralf/local/bin/m4:/tmp/auJL1116/unm4.m4:2: Warning: _au__undefine:
> > undefined macro `builtin'
> Which test names?  I'm looking into it now...

 17 19 20 21 25 26 28 failed

> > 
> > I assume that 2.62 will fail, too, thus M4 needs fixed or it won't be
> > compatible with Autoconf 2.62.
> Hopefully, it is just an incomplete patch on the autoconf side (I already 
> through several drafts on the autoconf side, after noticing that one of my 
> versions broke autoscan), and not a fundamental incompatibility between 1.6 
> 2.62.

Wow.  autoupdate and m4 2.0 have been incompatible for years now, with no one 
complaining.  It is only my recent change to 1.6 that finally exposed the 
brokenness.  And fortunately, the breakage is only in autoupdate, which is a 
much-less used piece of the Autoconf package.  At any rate, a one-liner fix got 
17-26 (I'm still looking at 28); I'll post the final patch to autoconf, then 
document a link to it in the m4 NEWS (similar to the link I added for the 
autoconf 2.59 incompatibility with m4wrap).  And this means that m4 1.6 can't 
be released until after autoconf 2.63 (not that it is too hard to ensure that, 
as I help maintain both...)

Eric Blake

reply via email to

[Prev in Thread] Current Thread [Next in Thread]