From: DJ Delorie <dj@delorie.com>
To: neroden@twcny.rr.com
Cc: gcc-patches@gcc.gnu.org, binutils@sources.redhat.com,
gdb-patches@sources.redhat.com
Subject: Re: (toplevel patch) Fix multilib.out dependencies and related problems
Date: Thu, 19 Dec 2002 18:08:00 -0000 [thread overview]
Message-ID: <200212200208.gBK28gw19118@envy.delorie.com> (raw)
In-Reply-To: <20021220015902.GA1721@doctormoo> (message from Nathanael Nerode on Thu, 19 Dec 2002 20:59:02 -0500)
> In other words, when multilib.out is considered 'out of date' and
> needs to be rebuilt, its rule is run. But if that rule doesn't
> change the datestamp on multilib.out, Make decides that the things
> depending on multilib.out, such as foo/Makefile, *don't* need to be
> rebuilt.
Yup. See gcc's Makefile for examples of how to do this.
They do it like this:
multilib.out : multilib.ts ; @true
multilib.ts : [dependencies]
foo > multilib.tmp
$(SHELL) $(srcdir)/move-if-change multilib.tmp multilib.out
echo timestamp > multilib.ts
The other multilib.out targets just depend on multilib.out:
$target/[module]/multlib.out : multilib.out
cp multilib.out $target/[module]/multilib.out
next prev parent reply other threads:[~2002-12-20 2:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-19 18:00 Nathanael Nerode
2002-12-19 18:08 ` DJ Delorie [this message]
2002-12-19 18:23 ` Zack Weinberg
-- strict thread matches above, loose matches on Subject: below --
2002-12-19 17:18 Nathanael Nerode
2002-12-19 17:29 ` DJ Delorie
2002-12-19 16:06 Nathanael Nerode
2002-12-19 16:16 ` DJ Delorie
2002-12-21 18:08 ` 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=200212200208.gBK28gw19118@envy.delorie.com \
--to=dj@delorie.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).