From: Phil Edwards <phil@jaj.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Nathanael Nerode <neroden@twcny.rr.com>,
gcc@gcc.gnu.org, gdb@sources.redhat.com,
binutils@sources.redhat.com, newlib@sources.redhat.com
Subject: Re: Planning for the Autoconf 2.5x transition?
Date: Thu, 26 Dec 2002 06:12:00 -0000 [thread overview]
Message-ID: <20021224215544.A15340@disaster.jaj.com> (raw)
In-Reply-To: <orznquzufr.fsf@free.redhat.lsd.ic.unicamp.br>; from aoliva@redhat.com on Wed, Dec 25, 2002 at 12:47:04AM -0200
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.
Phil
--
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
next prev parent reply other threads:[~2002-12-25 2:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-24 6:11 Nathanael Nerode
2002-12-26 5:47 ` Alexandre Oliva
2002-12-26 6:12 ` Phil Edwards [this message]
2002-12-30 7:34 ` Nick Clifton
2003-01-02 17:15 Benjamin Kosnik
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20021224215544.A15340@disaster.jaj.com \
--to=phil@jaj.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sources.redhat.com \
--cc=neroden@twcny.rr.com \
--cc=newlib@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).