From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4102 invoked by alias); 30 Mar 2004 00:53:51 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 4017 invoked from network); 30 Mar 2004 00:53:49 -0000 Received: from unknown (HELO mail-out4.apple.com) (17.254.13.23) by sources.redhat.com with SMTP; 30 Mar 2004 00:53:49 -0000 Received: from mailgate1.apple.com (a17-128-100-225.apple.com [17.128.100.225]) by mail-out4.apple.com (8.12.11/8.12.11) with ESMTP id i2U0upvj017605 for ; Mon, 29 Mar 2004 16:56:51 -0800 (PST) Received: from relay1.apple.com (relay1.apple.com) by mailgate1.apple.com (Content Technologies SMTPRS 4.3.6) with ESMTP id ; Mon, 29 Mar 2004 16:53:48 -0800 Received: from apple.com (mrs1.apple.com [17.201.24.248]) by relay1.apple.com (8.12.11/8.12.11) with ESMTP id i2U0rVPn005466; Tue, 30 Mar 2004 00:53:32 GMT Date: Tue, 30 Mar 2004 05:48:00 -0000 Subject: Re: [Newb] Building with debug info and no optimization Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v553) Cc: sashan , gcc@gcc.gnu.org To: Jim Wilson From: Mike Stump In-Reply-To: <4068BB33.4090102@specifixinc.com> Message-Id: Content-Transfer-Encoding: 7bit X-SW-Source: 2004-03/txt/msg01691.txt.bz2 On Monday, March 29, 2004, at 04:11 PM, Jim Wilson wrote: > sashan wrote: >> configure: error: `CFLAGS' has changed since the previous run: >> configure: former value: -g -O2 >> configure: current value: -g >> configure: error: changes in the environment can compromise the build >> configure: error: run `make distclean' and/or `rm ./config.cache' and >> start over > > If you look at the errors carefully, you will see that the problem is > not in the toplevel but rather in one of the subdirectories. So the > problem is not ./config.cache but rather subdir/config.cache, where > you can get subdir from the make output. You can try deleting them > one at a time, but if one is broken probably all are broken. So you > may want to try something like "rm */config.cache". > > It is probably safer to just configure a new tree though. Delete the > old build tree and configure a new one, instead of trying to > reconfigure a build tree after a cvs update. I think I hate the new code. :-( The times this kicks out errors from make; cvs update make; cvs update; make; cvs update is just annoying. In my experience, rm */config.cache; make restores the reliability of the operation.