From: Michal Marek <mmarek@suse.cz>
To: os user <gnusercn@gmail.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: question about kbuild system
Date: Mon, 23 May 2011 13:52:32 +0200 [thread overview]
Message-ID: <4DDA4A80.7040406@suse.cz> (raw)
In-Reply-To: <BANLkTi=7AiRbsVojWr=7VVS41EyFXaASGw@mail.gmail.com>
On 21.5.2011 14:45, os user wrote:
[...]
> Considering target file `scripts/basic/.fixdep.cmd'.
> Looking for an implicit rule for `scripts/basic/.fixdep.cmd'.
> Trying pattern rule with stem `.fixdep.cmd'.
> Trying implicit prerequisite `scripts/basic/.fixdep.cmd_shipped'.
> No implicit rule found for `scripts/basic/.fixdep.cmd'.
> Finished prerequisites of target file `scripts/basic/.fixdep.cmd'.
> No need to remake target `scripts/basic/.fixdep.cmd'.
> Considering target file `scripts/basic/.docproc.cmd'.
> [...]
>
> I'm just curious where is the definition for<implicit prerequisite
> `scripts/basic/.fixdep.cmd_shipped'> ?
> Normally Gnu Make will try a lot of internal rules to deal with
> <`scripts/basic/.fixdep.cmd'>, why here Gnu Make stop
> trying internal ruls so quickly?
Internal rules are disabled in kbuild, see the toplevel Makefile:
# Do not:
# o use make's built-in rules and variables
# (this increases performance and avoids hard-to-debug behaviour);
# o print "Entering directory ...";
MAKEFLAGS += -rR --no-print-directory
The rule for _shipped files is in scripts/Makefile.lib
Michal
prev parent reply other threads:[~2011-05-23 11:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 12:45 question about kbuild system os user
2011-05-23 11:52 ` Michal Marek [this message]
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=4DDA4A80.7040406@suse.cz \
--to=mmarek@suse.cz \
--cc=gnusercn@gmail.com \
--cc=linux-kbuild@vger.kernel.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