From: Andreas Schwab <schwab@suse.de>
To: Mike Stump <mrs@apple.com>
Cc: Jim Wilson <wilson@specifixinc.com>, sashan <sashang@ihug.co.nz>,
gcc@gcc.gnu.org
Subject: Re: [Newb] Building with debug info and no optimization
Date: Tue, 30 Mar 2004 17:36:00 -0000 [thread overview]
Message-ID: <jead1ymzuh.fsf@sykes.suse.de> (raw)
In-Reply-To: <A96062CE-81E4-11D8-A319-003065A77310@apple.com> (Mike Stump's message of "Mon, 29 Mar 2004 16:53:30 -0800")
Mike Stump <mrs@apple.com> writes:
> 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.
I think the problem is that configure-foo exports a different set of
envvars than all-foo. You can remove the sub makefiles to force rerunning
configure-foo from the toplevel.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
prev parent reply other threads:[~2004-03-30 9:46 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
2004-03-30 17:36 ` Andreas Schwab [this message]
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=jead1ymzuh.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gcc@gcc.gnu.org \
--cc=mrs@apple.com \
--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).