This is the mail archive of the gdb@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Why autoconf 2.13?

From: DJ Delorie <dj at redhat dot com>
To: schwab at suse dot de
Cc: gdb at sources dot redhat dot com
Date: Fri, 12 Apr 2002 11:19:55 -0400
Subject: Re: Why autoconf 2.13?
References: <200204110039.g3B0dCT03033@fred.ninemoons.com><xnzo0agkez.fsf@greed.delorie.com> <87lmbtoq9r.fsf@creche.redhat.com><xnr8llhn0d.fsf@greed.delorie.com> <jeads9z0ix.fsf@sykes.suse.de>


> 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.

Follow-Ups:
- Re: Why autoconf 2.13?
  - From: Andreas Schwab

References:
- Why autoconf 2.13?
  - From: Fred Fish
- Re: Why autoconf 2.13?
  - From: DJ Delorie
- Re: Why autoconf 2.13?
  - From: Tom Tromey
- Re: Why autoconf 2.13?
  - From: DJ Delorie
- Re: Why autoconf 2.13?
  - From: Andreas Schwab

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]