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

Alex said:
>- I've also removed the dependence of configure-* on ./config.status.
>  I don't understand why we put this in.  I get the impression it was
>  a mistake, since the earlier top-level (say in the gcc-3.3 branch)
>  does not get any sub-packages reconfigured just because the top
>  level config.status changes.  If we really want to do this, we
>  should arrange for the code that updates config.status in the
>  top-level to also remove the Makefiles of all subdirs, so that
>  they're reconfigured next.

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

The correct dependence, technically, is that configure-* depends on top 
level Makefile, which depends on config.status.

The point is, if you rerun top level 'configure' with different 
arguments, creating a new Makefile which will pass down different 
arguments, it's essential to rerun configure at the lower levels with 
the new arguments as well.  

Implement this however you please, but it needs to be there. :-)

--Nathanael


             reply	other threads:[~2002-12-30 10:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-30  2:42 Nathanael Nerode [this message]
2002-12-30  6:25 ` Alexandre Oliva
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=20021230103438.GA371@doctormoo \
    --to=neroden@twcny.rr.com \
    --cc=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@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