From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2291 invoked by alias); 12 Apr 2002 16:07:20 -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 2271 invoked from network); 12 Apr 2002 16:07:18 -0000 Received: from unknown (HELO localhost.redhat.com) (24.112.240.27) by sources.redhat.com with SMTP; 12 Apr 2002 16:07:18 -0000 Received: from cygnus.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id F35B63CD8; Fri, 12 Apr 2002 12:07:22 -0400 (EDT) Message-ID: <3CB7063A.4090409@cygnus.com> Date: Fri, 12 Apr 2002 09:07:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:0.9.9) Gecko/20020328 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andreas Schwab Cc: DJ Delorie , gdb@sources.redhat.com Subject: Re: Why autoconf 2.13? References: <200204110039.g3B0dCT03033@fred.ninemoons.com> <87lmbtoq9r.fsf@creche.redhat.com> <200204121519.g3CFJtg03564@greed.delorie.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2002-04/txt/msg00217.txt.bz2 > DJ Delorie writes: > > |> > 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. > > I still regard it as an acceptable workaround, since the data in it can > become stale quite easily anyway, just by changing anything in the build > environment. Yes. If an update contains autoconf changes, I always end up rebuilding from scratch. Andrew