Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Geoff Keating <geoffk@geoffk.org>
To: Andrew Cagney <ac131313@redhat.com>
Cc: binutils@sources.redhat.com, gdb@sources.redhat.com, dje@transmeta.com
Subject: Re: ^c now disallowed? (was Re: "cd dir && $(MAKE)", not "cd dir; $(MAKE)")
Date: Thu, 02 Jan 2003 17:28:00 -0000	[thread overview]
Message-ID: <jmhecrjwbs.fsf@desire.geoffk.org> (raw)
In-Reply-To: <3E14530E.90809@redhat.com>

Andrew Cagney <ac131313@redhat.com> writes:

> In the past, with separate configure / build phases, this was easy -
> cntrl-c the configure and blow away the directory tree.  Now, with the
> configure phases intermingled with the build phases, doing this has
> become that much harder.
> 
> All that is hopefully needed is a bit of dependency tweaking - touch
> something after the configure phase completes and depend on that.

Ideally, if one wanted to build GDB and not GCC (for instance), it
would be as easy as saying 'make all-gdb'.  Since the Makefile now
runs configure, the GCC configury shouldn't be run.

I do think that 'make ; ^c ; make' should work.  The ^c might be
something like 'disk full' or 'oops, foo/configure fails with exit 1'
or 'oops, cc1 has the wrong permissions'.

-- 
- Geoffrey Keating <geoffk@geoffk.org>


  reply	other threads:[~2003-01-02 17:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-27 20:16 Nathanael Nerode
2003-01-02 14:56 ` Andrew Cagney
2003-01-02 17:28   ` Geoff Keating [this message]
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=jmhecrjwbs.fsf@desire.geoffk.org \
    --to=geoffk@geoffk.org \
    --cc=ac131313@redhat.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