Date: Tue, 3 Jun 2003 21:06:29 +0100
From: Stig Brautaset <stig@brautaset.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: strange dependancy generation bug?
Message-ID: <20030603200629.GA30842@brautaset.org>
References: <fa.er84418.1ikmjqq@ifi.uio.no> <fa.hfbafvn.n7qkih@ifi.uio.no> <20030603191154.GA30323@brautaset.org> <20030603195651.GA17845@mars.ravnborg.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20030603195651.GA17845@mars.ravnborg.org>
User-Agent: Mutt/1.5.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1553
Lines: 41

On Jun 03 2003, Sam wrote:
> On Tue, Jun 03, 2003 at 08:11:54PM +0100, Stig Brautaset wrote:
> > > What happens is that within Makefile.build there is used multi line
> > > definition, where each new-line causes make to launch a new sub-shell.
> > > The command for the second sub-shell is echoed, even though make is told
> > > not to do so. 
> > 
> > I beg to differ. Since make launches a new subshell, the commands in the
> > second subshell is _not_ told to shut up, and thus is echoed. No?
> 
> In make a so-called "canned command sequence" is generated.
> Quote from 'info make':
> 
> 	On the other hand, prefix characters on the command line that refers
> 	to a canned sequence apply to every line in the sequence.  So the rule:
> 
> 	     frob.out: frob.in
>         	     @$(frobnicate)
> 
> 	does not echo _any_ commands.
> 
> 
> In kbuild this is exactly what happens.
> So according to make info the command for the second sub-shell should not
> be echoed.

Indeed. It seem I haven't read the docs carefully enough. I was just
looking at cause and effect -- not how it's _supposed_ to work. ;) 

Here, with two subshells, the latter part is echoed, with one it is not. 
However, in the light of this (to me) new information I'm at a loss as
to what causes this to happen.

Stig
-- 
brautaset.org
-
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/