From: DJ Delorie <dj@redhat.com>
To: gdb@sources.redhat.com
Subject: Re: Why autoconf 2.13?
Date: Thu, 11 Apr 2002 11:30:00 -0000 [thread overview]
Message-ID: <xnzo0agkez.fsf@greed.delorie.com> (raw)
In-Reply-To: <200204110039.g3B0dCT03033@fred.ninemoons.com>
Fred Fish <fnf@fred.ninemoons.com> writes:
> Is there some reason that gdb is using a 3 year old version of
> autoconf instead of the latest official FSF release (2.53 I think)?
There are problems with autoconf 2.5x reading a config.cache from
2.13. I haven't heard any word about that being fixed. Plus, it's a
good idea to support the most recent 2 major releases, and 2.13 is
still in that category. It's also the autoconf that's preinstalled on
Red Hat Linux 7.2.
We don't automatically start using newer support tools just because
they've been released. We need a compelling reason to force all the
users to upgrade their machines, and we haven't seen one yet.
next prev parent reply other threads:[~2002-04-11 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 17:38 Fred Fish
2002-04-10 17:41 ` Daniel Jacobowitz
2002-04-10 17:47 ` Christopher Faylor
2002-04-11 11:30 ` DJ Delorie [this message]
2002-04-11 15:00 ` Tom Tromey
2002-04-11 16:00 ` DJ Delorie
2002-04-12 3:14 ` Andreas Schwab
2002-04-12 8:19 ` DJ Delorie
2002-04-12 8:45 ` Andreas Schwab
2002-04-12 9:07 ` Andrew Cagney
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=xnzo0agkez.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=gdb@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