Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Raja R Harinath <harinath@cs.umn.edu>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc-patches@gcc.gnu.org, dj@redhat.com,
	binutils@sources.redhat.com, gdb-patches@sources.redhat.com
Subject: Re: (toplevel patch) Deal with multilib.out.  Really.
Date: Fri, 20 Dec 2002 01:35:00 -0000	[thread overview]
Message-ID: <d9wum5w7wk.fsf@bose.cs.umn.edu> (raw)
In-Reply-To: <20021220022225.GA2130@doctormoo> (Nathanael Nerode's message of "Thu, 19 Dec 2002 21:22:25 -0500")

Hi,

Nathanael Nerode <neroden@twcny.rr.com> writes:

> +# Multilib.out tells target dirs what multilibs they should build.
> +# There is really only one copy.  We use the 'timestamp' method to
> +# work around various timestamp bugs on some systems.
> +# We use move-if-change so that it's only considered updated when it
> +# actually changes, because it has to depend on a phony target.
> +multilib.out: multilib.ts
> +	@true

To round out this idiom, this should be

  multilib.out: multilib.ts
	@if test -f multilib.out; then :; \
        else rm -f multilib.ts; $(MAKE) multilib.ts; fi

So that

  rm multilib.out
  make

works.  

Also, IIRC discussions on the automake list about the use of 'then :;
else' form rather than 'test ! -f' -- some shells use the exit code of
the 'if' test when they fall through a missing 'else' clause.

- Hari
-- 
Raja R Harinath ------------------------------ harinath@cs.umn.edu


      reply	other threads:[~2002-12-20  5:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-19 18:33 Nathanael Nerode
2002-12-20  1:35 ` Raja R Harinath [this message]

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=d9wum5w7wk.fsf@bose.cs.umn.edu \
    --to=harinath@cs.umn.edu \
    --cc=binutils@sources.redhat.com \
    --cc=dj@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