From: Stig Brautaset <stig@brautaset.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: strange dependancy generation bug?
Date: Tue, 3 Jun 2003 21:06:29 +0100 [thread overview]
Message-ID: <20030603200629.GA30842@brautaset.org> (raw)
In-Reply-To: <20030603195651.GA17845@mars.ravnborg.org>
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
next prev parent reply other threads:[~2003-06-03 19:57 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 ` strange dependancy generation bug? Stig Brautaset
2003-06-03 19:56 ` Sam Ravnborg
2003-06-03 20:06 ` Stig Brautaset [this message]
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=20030603200629.GA30842@brautaset.org \
--to=stig@brautaset.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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