Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
	binutils@sources.redhat.com
Subject: Re: subdir/toplevel dependence (was Re: (toplevel)...)
Date: Mon, 30 Dec 2002 06:25:00 -0000	[thread overview]
Message-ID: <oru1gvppnc.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20021230103438.GA371@doctormoo>

On Dec 30, 2002, Nathanael Nerode <neroden@twcny.rr.com> wrote:

> I put this in because there's a real dependence here. :-(

Thanks, I see it now.  It just happened to trigger other unwanted
dependencies, that I really disliked.  Well, guess we'll have to put
them back in, but perhaps we can be more clever.

The idea is to force sub-configures to run whenever we run the
top-level configure, but if it's rerun just because the top-level
configure was updated, we don't have to rerun sub-configures, right?
That's the way it used to be.

The solution I see is to arrange for configure to remove sub-Makefiles
if it is run without --no-recursion (i.e., no_recursion != yes).
Then, the check for sub-Makefile in the configure-* targets will take
care of reconfiguring.  How does this sound?

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                 aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist                Professional serial bug killer


  reply	other threads:[~2002-12-30 14:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-30  2:42 Nathanael Nerode
2002-12-30  6:25 ` Alexandre Oliva [this message]
2002-12-30  7:46 Nathanael Nerode
2003-01-09 20:44 ` 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=oru1gvppnc.fsf@free.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@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