mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Stig Brautaset <stig@brautaset.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: strange dependancy generation bug?
Date: Tue, 3 Jun 2003 21:56:51 +0200	[thread overview]
Message-ID: <20030603195651.GA17845@mars.ravnborg.org> (raw)
In-Reply-To: <20030603191154.GA30323@brautaset.org>

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.

	Sam

  reply	other threads:[~2003-06-03 19:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.er84418.1ikmjqq@ifi.uio.no>
     [not found] ` <fa.hfbafvn.n7qkih@ifi.uio.no>
2003-06-03 19:11   ` Stig Brautaset
2003-06-03 19:56     ` Sam Ravnborg [this message]
2003-06-03 20:06       ` Stig Brautaset
2003-06-04  0:43       ` Ricky Beam
2003-06-03 12:07 Dave Jones
2003-06-03 18:29 ` Sam Ravnborg

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=20030603195651.GA17845@mars.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stig@brautaset.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

all inboxes | Powered by JetHome®