[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Aclocal bug?
From: |
Eric Blake-1 |
Subject: |
Re: Aclocal bug? |
Date: |
Thu, 9 Nov 2006 10:03:50 -0800 (PST) |
>
> > I think that Autoconf should require m4 >= 1.4.5.
> >
> > (Autoconf's confgiure should check for it; should it be done in
> > m4/m4.m4 in AM_PROG_GNU_M4, or in configure.ac?)
>
> I agree. Both when building and installing the tools from source,
> autoconf's configure should complain if the installed m4 is not new
> enough; and also when bootstrapping Autoconf itself, a diagnostic for
> too old a GNU M4 should given when necessary.
For that matter, a configure.ac that contains:
m4_indir([AM_GNU_GETTEXT_INTL_SUBDIR])
can trigger a coredump in m4 1.4.4 or earlier with CVS
autoconf.
However, m4 1.4.5 only came out this summer, and it
seems a bit scary to make autoconf 2.61 depend on something
that is not at least a year old. But it is worth serious thought
to having autoconf 2.61 require newer m4, since we have shown
that otherwise, a common usage pattern of gettext is broken.
Making this dependency will likely force Apple and others to
upgrade their provided m4 at the same time they upgrade to
autoconf 2.61.
--
Eric Blake
--
View this message in context:
http://www.nabble.com/Re%3A-Aclocal-bug--tf2602172.html#a7263116
Sent from the Gnu - Autoconf - Bugs mailing list archive at Nabble.com.