From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kbuild-permanently-fix-kernel-configuration-include-mess.patch added to -mm tree
Date: Wed, 14 Sep 2005 17:53:26 +0100 [thread overview]
Message-ID: <20050914175326.C30746@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050914164953.GA7480@mars.ravnborg.org>; from sam@ravnborg.org on Wed, Sep 14, 2005 at 06:49:53PM +0200
On Wed, Sep 14, 2005 at 06:49:53PM +0200, Sam Ravnborg wrote:
> > # Use LINUXINCLUDE when you must reference the include/ directory.
> > # Needed to be compatible with the O= option
> > LINUXINCLUDE := -Iinclude \
> > - $(if $(KBUILD_SRC),-Iinclude2 -I$(srctree)/include)
> > + $(if $(KBUILD_SRC),-Iinclude2 -I$(srctree)/include) \
> > + -imacros include/linux/autoconf.h
> >
> What is the purpose of using -imacros instead of -iinclude
>
> o -iinclude is much more commonly used for this purpose.
> o sparse has limited support(*) for -iinclude today
> o -imacros will silently ignore any output caused by the file
autoconf.h should only be macro definitions and should not contain
any code, so -imacros seemed to be the correct tool for the job.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-09-14 16:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200509140841.j8E8fG1w022954@shell0.pdx.osdl.net>
2005-09-14 9:05 ` kbuild-permanently-fix-kernel-configuration-include-mess.patch added to -mm tree Coywolf Qi Hunt
2005-09-14 9:20 ` Russell King
2005-09-14 10:58 ` Alan Cox
2005-09-14 17:26 ` Sam Ravnborg
2005-09-14 16:49 ` Sam Ravnborg
2005-09-14 16:53 ` Russell King [this message]
2005-09-14 16:58 ` 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=20050914175326.C30746@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.