linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: cpclark@xmission.com
Cc: Tom Rini <trini@kernel.crashing.org>,
	Linux Kernel list <linux-kernel@vger.kernel.org>,
	linuxppc-embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: PPC uImage build not reporting correctly
Date: Wed, 11 May 2005 07:01:19 +0200	[thread overview]
Message-ID: <20050511050119.GC8025@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0505100420380.8140@xmission.xmission.com>

 >
> > Looks ok - but I do not see why use of $(shell ...) did not work out.
> 
> As I understand it, the $(shell ...) construct doesn't "work" in the case 
> cited above because make evaluates/expands the $(shell ...) stuff while it 
> is parsing the makefile and building the command list--i.e. before it has 
> issued any commands to build anything.  What seems to be desired in this 
> case is a file-existence test which runs "inline" with respect to the 
> preceding commands.  The use of $(shell ...) inside a command 
> subverts/preempts that natural sequence.  I think. :-)

That explains it - thanks!

	Sam

  reply	other threads:[~2005-05-11  4:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.63.0505061718380.6288@xmission.xmission.com>
2005-05-09 15:19 ` PPC uImage build not reporting correctly Kumar Gala
2005-05-10  4:28   ` Sam Ravnborg
2005-05-10 10:34     ` cpclark
2005-05-11  5:01       ` Sam Ravnborg [this message]
2005-05-10 15:14 Stephen Warren
  -- strict thread matches above, loose matches on Subject: below --
2005-05-06 15:23 Kumar Gala
2005-05-06 21:45 ` Sam Ravnborg
2005-05-06 21:57   ` Kumar Gala

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=20050511050119.GC8025@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=cpclark@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=trini@kernel.crashing.org \
    /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 NNTP newsgroup(s).