public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
		Hans-Peter Nilsson <hp@bitrange.com>,
		Thiemo Seufer <ths@networkno.de>,
		GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Don't hardcode the makefile name in config-ml.in
Date: Mon, 26 Nov 2007 14:47:00 -0000	[thread overview]
Message-ID: <jesl2tff2t.fsf@sykes.suse.de> (raw)
In-Reply-To: <474AA476.7020605@gnu.org> (Paolo Bonzini's message of "Mon\, 26 	Nov 2007 11\:48\:22 +0100")

Paolo Bonzini <bonzini@gnu.org> writes:

> If I understand correctly, the ${Makefile} in
>
> 	  for dir in ${Makefile} $(MULTIDIRS); do \
>
> is just a way to avoid an error if MULTIDIRS is empty but [ -z 
> "$(MULTIDIRS)" ] does not get it?

It would be a syntax error in some shells, and the test is part of the
same command, so the loop command would be parsed nevertheless.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

  reply	other threads:[~2007-11-26 10:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-19 10:24 Thiemo Seufer
2007-11-19 10:49 ` Paolo Bonzini
2007-11-26  6:44 ` Hans-Peter Nilsson
2007-11-26 10:48   ` Ralf Wildenhues
2007-11-26 14:17     ` Paolo Bonzini
2007-11-26 14:47       ` Andreas Schwab [this message]
2007-11-26 15:04       ` Ralf Wildenhues
2007-11-26 15:20         ` Paolo Bonzini

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=jesl2tff2t.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hp@bitrange.com \
    --cc=ths@networkno.de \
    /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).