Re: any reason not to enforce the build requirement: m4 >= 1.4.4 ?

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

 



Eric Blake <ebb9@xxxxxxx> wrote:
> According to Jim Meyering on 2/1/2007 9:37 AM:
>> I spent some time recently tracking down a bug that arose from an autoconf
>> installation built using m4-1.4.2.  My testing showed that autoconf built
>> using any version of m4 older than 1.4.4 would have the same problem.
>
> What bug was it?
...
> http://lists.gnu.org/archive/html/m4-patches/2006-11/msg00028.html

It was that exact same one, by the looks of that patch.
I checked my notes and do see the problem also affected 1.4.4.

> Maybe it is time to bite the bullet and modify that test into autoconf's
> m4/m4.m4 so that autoconf 2.62 has a hard requirement on m4 1.4.5 or newer?

No "maybe" about it.  It's overdue.


_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf

[Index of Archives]     [GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [Linux USB]     [Samba]

  Powered by Linux