From: DJ Delorie <dj@redhat.com>
To: neroden@twcny.rr.com
Cc: gcc-patches@gcc.gnu.org, gdb-patches@sources.redhat.com,
binutils@sources.redhat.com
Subject: Re: (toplevel patch) Fix multilib.out dependencies and related problems.
Date: Thu, 19 Dec 2002 17:18:00 -0000 [thread overview]
Message-ID: <200212200016.gBK0GL424979@greed.delorie.com> (raw)
In-Reply-To: <20021220000447.GA18896@doctormoo> (message from Nathanael Nerode on Thu, 19 Dec 2002 19:04:47 -0500)
> Removed xgcc and ran 'make'; gcc rebuilt it, and target libs were
> reconfigured and built.
That shouldn't happen. Use move-if-change to update one common
multilib.out, so that if the list of multilibs doesn't change,
*nothing* gets reconfigured or rebuilt. We want to trigger a *check*
when gcc changes, but only actually *reconfigure* if needed.
I'm wondering if the common multilib.out target should depend on the
all-gcc phony target; we kinda want it to run every time we check the
gcc subdir, because we don't know if something else besides xgcc
affects the specs (which affects multilib.out). We can get away with
this if we use move-if-change.
next prev parent reply other threads:[~2002-12-20 0:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 16:16 Nathanael Nerode
2002-12-19 17:18 ` DJ Delorie [this message]
2002-12-21 19:02 ` Alexandre Oliva
2002-12-19 17:29 Nathanael Nerode
2002-12-19 18:00 ` DJ Delorie
2002-12-19 18:08 Nathanael Nerode
2002-12-19 18:23 ` DJ Delorie
2002-12-19 18:24 ` Zack Weinberg
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=200212200016.gBK0GL424979@greed.delorie.com \
--to=dj@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