From: Sam Ravnborg <sam@ravnborg.org>
To: "Yang, Fei" <fei.yang@intel.com>
Cc: Michal Marek <mmarek@suse.cz>,
"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>,
"'linux-kernel@vger.kernel.org' (linux-kernel@vger.kernel.org)"
<linux-kernel@vger.kernel.org>
Subject: Re: Can anyone suggest a better fix? Not sure if I understand the problem, but the patch fixed it
Date: Thu, 29 Aug 2013 19:55:11 +0200 [thread overview]
Message-ID: <20130829175511.GA23620@merkur.ravnborg.org> (raw)
In-Reply-To: <02E7334B1630744CBDC55DA85862258348E4792D@ORSMSX102.amr.corp.intel.com>
>
> I thought fixdep is about finding module dependency, and
> it isn't needed for built-in drivers.
> Please correct me if I'm wrong.
You are wrong...
Fixdep conatins all the dependencies used to determine if we shall rebuild foo.o.
It has nothing to do with modules or not.
Following happens when you build foo.o from foo.c:
1) gcc -Wp,-MD,foo.o.d foo.c -o foo.o
This produces two files:
foo.o.d - contains all files included by foo.c, recursive (try it out!)
foo.o - the object file
2) fixdep foo.o.d foo.o gcc -Wp,-MD,foo.o.d foo.c -o foo.o > foo.o.tmp
fixdep now does the following:
- Assign the comandline to a variable
- List all dependencies (files included)
- Scan the dependen file for CONFIG_* symbols
- for each CONFIG_* symbol add a $(wildcard ...) reference to a symbol in
include/generated/config/... that represents the CONFIG_ symbol
Everything is stored in foo.o.tmp
3) delete foo.o.cmd
4) rename foo.o.tmp to foo.o.cmd
Magic happens in Kbuild.include, Makefile.lib and Makefile.build.
But it make take some cup of coffee to grasp it.
For find and fix whatever race condition you hit.
Sam
next prev parent reply other threads:[~2013-08-29 17:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 19:22 Yang, Fei
2013-08-26 20:10 ` Sam Ravnborg
2013-08-27 19:05 ` Yang, Fei
2013-08-28 15:07 ` Michal Marek
2013-08-28 15:08 ` Michal Marek
2013-08-28 16:27 ` Yang, Fei
2013-08-28 16:31 ` Michal Marek
2013-08-28 16:47 ` Yang, Fei
2013-08-29 17:55 ` Sam Ravnborg [this message]
2013-08-30 15:10 ` Michal Marek
2013-08-29 17:55 ` 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=20130829175511.GA23620@merkur.ravnborg.org \
--to=sam@ravnborg.org \
--cc=fei.yang@intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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®