From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17005 invoked by alias); 12 Apr 2002 15:19:59 -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 16998 invoked from network); 12 Apr 2002 15:19:58 -0000 Received: from unknown (HELO cygnus.com) (205.180.83.203) by sources.redhat.com with SMTP; 12 Apr 2002 15:19:58 -0000 Received: from greed.delorie.com (cse.sfbay.redhat.com [205.180.230.236]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id IAA02024; Fri, 12 Apr 2002 08:19:56 -0700 (PDT) Received: (from dj@localhost) by greed.delorie.com (8.11.6/8.11.6) id g3CFJtg03564; Fri, 12 Apr 2002 11:19:55 -0400 Date: Fri, 12 Apr 2002 08:19:00 -0000 Message-Id: <200204121519.g3CFJtg03564@greed.delorie.com> From: DJ Delorie To: schwab@suse.de CC: gdb@sources.redhat.com In-reply-to: (message from Andreas Schwab on Fri, 12 Apr 2002 12:14:46 +0200) Subject: Re: Why autoconf 2.13? References: <200204110039.g3B0dCT03033@fred.ninemoons.com> <87lmbtoq9r.fsf@creche.redhat.com> X-SW-Source: 2002-04/txt/msg00212.txt.bz2 > What's wrong with "rm config.cache"? autoconf 2.50+ does not even create > a config.cache by default any more. The problem is when someone does "cvs update" and suddenly everything breaks because they got a newly configured configure which doesn't like the config.cache they've got sitting around.