From: Doug Evans <dje@transmeta.com>
To: neroden@twcny.rr.com
Cc: gdb@sources.redhat.com
Cc: binutils@sources.redhat.com
Subject: ^c now disallowed? (was Re: "cd dir && $(MAKE)", not "cd dir; $(MAKE)")
Date: Fri, 27 Dec 2002 11:16:00 -0000 [thread overview]
Message-ID: <200212271914.LAA04845@casey.transmeta.com> (raw)
Browsing the gdb archives I came across this.
Nathanael Nerode writes:
> But interrupting 'make' in the middle can give
> all manner of screwy results now; don't rely on it.
Ugh. This is an effect of the configury change that
I hadn't anticipated. This is going to be a major pain IMHO.
Are the powers that be really ok with saying "just don't do that (*1)" ?
(*1): Which is effectively the same as saying rm -rf *
(assuming objdir != srcdir of course) is required if
you ^c and want the next `make' to work (assuming you don't want to
go to the trouble of figuring out what state the tree is in that will
screw up a subsequent make). Ugh.
next reply other threads:[~2002-12-27 19:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 11:16 Doug Evans [this message]
2002-12-27 11:47 ` DJ Delorie
2002-12-27 12:42 ` Doug Evans
2002-12-27 12:46 ` DJ Delorie
2002-12-27 20:16 Nathanael Nerode
2003-01-02 14:56 ` Andrew Cagney
2003-01-02 17:28 ` Geoff Keating
2003-01-02 20:10 ` Alexandre Oliva
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=200212271914.LAA04845@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=gdb@sources.redhat.com \
--cc=neroden@twcny.rr.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