From: Mike Stump <mrs@apple.com>
To: Jim Wilson <wilson@specifixinc.com>
Cc: sashan <sashang@ihug.co.nz>, gcc@gcc.gnu.org
Subject: Re: [Newb] Building with debug info and no optimization
Date: Tue, 30 Mar 2004 05:48:00 -0000 [thread overview]
Message-ID: <A96062CE-81E4-11D8-A319-003065A77310@apple.com> (raw)
In-Reply-To: <4068BB33.4090102@specifixinc.com>
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.
next prev parent reply other threads:[~2004-03-30 0:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 4:11 sashan
2004-03-20 4:29 ` Ian Lance Taylor
2004-03-30 1:16 ` Jim Wilson
2004-03-30 5:48 ` Mike Stump [this message]
2004-03-30 17:36 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A96062CE-81E4-11D8-A319-003065A77310@apple.com \
--to=mrs@apple.com \
--cc=gcc@gcc.gnu.org \
--cc=sashang@ihug.co.nz \
--cc=wilson@specifixinc.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).