From: free.amit.kumar@gmail.com (Amit Kumar)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Which header file?
Date: Thu, 17 Nov 2016 07:38:20 +0000 [thread overview]
Message-ID: <CAPTh4Ovkb2bj9cYUbo+jVQtEMpo0coMUd4-1+G0BaHBtTOptAA@mail.gmail.com> (raw)
In-Reply-To: <90356.1479339048@turing-police.cc.vt.edu>
On Thu, Nov 17, 2016 at 5:00 AM <Valdis.Kletnieks@vt.edu> wrote:
> On Wed, 16 Nov 2016 21:01:19 +0000, Amit Kumar said:
>
> > In linux/include/linux/atomic.h, there are two files included
> asm/atomic.h
> > and asm/barrier.h. Both files are present in linux/include/asm-generic
> and
> > linux/arch/arm/include/asm. If I build like,
> > CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm make zImage dtbs
> > then which file is being used.
>
> Hint 1: Check for symlinks.
> Hint 2: Compile with 'make V=1' which will show the complete gcc command
> line,
>
Thank you for your hints.
I have used omap2plus_defconfig. After issuing command,
CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm make zImage dtbs V=1 | tee
mybuild.log
I have got something like this,
...
-nostdinc -isystem /usr/lib/gcc-cross/arm-linux-gnueabi/5/include
-I./arch/arm/include -I./arch/arm/include/generated/uapi
-I./arch/arm/include/generated -I./include -I./arch/arm/include/uapi
-I./include/uapi -I./include/generated/uapi -include
./include/linux/kconfig.h
...
First all -I is searched sequentially then -isystem dir is searched.
One additional thing I found that every file includes
./include/linux/kconfig.h which in turn includes generated/kconfig.h, which
I think is generated on the basis of .config, to check features enabled.
so you can see the order of -I parameters.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20161117/2bb6e712/attachment.html
prev parent reply other threads:[~2016-11-17 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 21:01 Which header file? Amit Kumar
2016-11-16 23:30 ` Valdis.Kletnieks at vt.edu
2016-11-17 7:38 ` Amit Kumar [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=CAPTh4Ovkb2bj9cYUbo+jVQtEMpo0coMUd4-1+G0BaHBtTOptAA@mail.gmail.com \
--to=free.amit.kumar@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).