From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11016 invoked by alias); 11 Apr 2002 18:30:19 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 10972 invoked by uid 22784); 11 Apr 2002 18:30:16 -0000 From: DJ Delorie Newsgroups: cygnus.gdb Subject: Re: Why autoconf 2.13? Date: Thu, 11 Apr 2002 11:30:00 -0000 Organization: Red Hat, Inc Message-ID: References: <200204110039.g3B0dCT03033@fred.ninemoons.com> NNTP-Posting-Host: cse.sfbay.redhat.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: cronkite.cygnus.com 1018549668 9836 205.180.230.236 (11 Apr 2002 18:27:48 GMT) X-Complaints-To: postmaster@cygnus.com NNTP-Posting-Date: 11 Apr 2002 18:27:48 GMT User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 To: gdb@sources.redhat.com DJ-Gateway: from newsgroup cygnus.gdb X-SW-Source: 2002-04/txt/msg00169.txt.bz2 Fred Fish 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.