From: Nathanael Nerode <neroden@twcny.rr.com>
To: binutils@sources.redhat.com, gdb@sources.redhat.com
Cc: dje@transmeta.com
Subject: Re: ^c now disallowed? (was Re: "cd dir && $(MAKE)", not "cd dir; $(MAKE)")
Date: Fri, 27 Dec 2002 20:16:00 -0000 [thread overview]
Message-ID: <20021228041443.GA3199@doctormoo> (raw)
>> To me there are legitimate reasons why a developer would want
>> "make ; ^c ; make" to work.
>
>I agree.
>
>> If by "key files" you mean "the target of the rule" I _think_ we're
>ok.
>
>I'm thinking that some rules might alter non-target files (like
>config.cache for configure), which might cause problems.
If you didn't interrupt a subconfigure pass, you should be fine.
If you did, you should delete the appropriate config.cache, the
appropriate Makefile, and anything else generated or modified by that
'configure', and then you should be fine. At least that's my belief.
--Nathanael
next reply other threads:[~2002-12-28 4:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 20:16 Nathanael Nerode [this message]
2003-01-02 14:56 ` Andrew Cagney
2003-01-02 17:28 ` Geoff Keating
2003-01-02 20:10 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2002-12-27 11:16 Doug Evans
2002-12-27 11:47 ` DJ Delorie
2002-12-27 12:42 ` Doug Evans
2002-12-27 12:46 ` DJ Delorie
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=20021228041443.GA3199@doctormoo \
--to=neroden@twcny.rr.com \
--cc=binutils@sources.redhat.com \
--cc=dje@transmeta.com \
--cc=gdb@sources.redhat.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