Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261879AbVEKE75 (ORCPT ); Wed, 11 May 2005 00:59:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261881AbVEKE75 (ORCPT ); Wed, 11 May 2005 00:59:57 -0400 Received: from pfepa.post.tele.dk ([195.41.46.235]:47169 "EHLO pfepa.post.tele.dk") by vger.kernel.org with ESMTP id S261879AbVEKE74 (ORCPT ); Wed, 11 May 2005 00:59:56 -0400 Date: Wed, 11 May 2005 07:01:19 +0200 From: Sam Ravnborg To: cpclark@xmission.com Cc: Kumar Gala , linuxppc-embedded list , Tom Rini , Linux Kernel list Subject: Re: PPC uImage build not reporting correctly Message-ID: <20050511050119.GC8025@mars.ravnborg.org> References: <20050510042828.GA8398@mars.ravnborg.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.8i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 861 Lines: 19 > > > 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/