This is the mail archive of the
mailing list for the binutils project.
Re: Planning for the Autoconf 2.5x transition?
- From: Phil Edwards <phil at jaj dot com>
- To: Alexandre Oliva <aoliva at redhat dot com>
- Cc: Nathanael Nerode <neroden at twcny dot rr dot com>, gcc at gcc dot gnu dot org, gdb at sources dot redhat dot com, binutils at sources dot redhat dot com, newlib at sources dot redhat dot com
- Date: Tue, 24 Dec 2002 21:55:44 -0500
- Subject: Re: Planning for the Autoconf 2.5x transition?
- References: <20021224055606.GA957@doctormoo> <email@example.com>
On Wed, Dec 25, 2002 at 12:47:04AM -0200, Alexandre Oliva wrote:
> This is possible, but it takes some additional effort because of
> caching issues. The one that comes to mind is that some early 2.5x
> versions of autoconf
> I'm not sure this was actually `fixed' in newer versions of
> autoconf 2.5x.
If we're going to jump to something more recent than 2.13, we may as well
require a /fixed/ recent version.
Put another way, I'm assuming and suggesting that when we talk about "2.5x
and later" we're doing so only because we haven't decided what x will be.
/Not/ because we're going to try and support all versions of x>=0.
I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
- Edsger Dijkstra, 1930-2002