From: Michal Marek <mmarek@suse.cz>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: -I option expansion and -Wmissing-include-dirs
Date: Sun, 11 Dec 2011 21:59:23 +0100 [thread overview]
Message-ID: <4EE519AB.20402@suse.cz> (raw)
In-Reply-To: <20111125134617.GA31133@shutemov.name>
On 25.11.2011 14:46, Kirill A. Shutemov wrote:
> Hi,
>
> Currently, kbuild makes -I option expansion without any check if the
> resulting include directory exists. It produce warnings if you try to build
> with W=1 which enables -Wmissing-include-dirs. For example:
>
> $ make W=1 O=~/var/tmp drivers/gpu/drm/drm_auth.o
> Using /home/space/kas/git/public/linux as source for kernel
> GEN /home/space/kas/var/tmp1/Makefile
> CHK include/linux/version.h
> CHK include/generated/utsrelease.h
> CALL /home/space/kas/git/public/linux/scripts/checksyscalls.sh
> CC [M] drivers/gpu/drm/drm_auth.o
> cc1: warning: include/drm: No such file or directory [enabled by default]
>
> It would be nice to address the issue.
That's not a kbuild bug but a drm Makefile bug. It should be passing
-I$(src)/include/drm. But it apparently builds even with the wrong
argument, so it can probably go away.
Michal
prev parent reply other threads:[~2011-12-11 20:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 13:46 -I option expansion and -Wmissing-include-dirs Kirill A. Shutemov
2011-12-11 20:59 ` 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=4EE519AB.20402@suse.cz \
--to=mmarek@suse.cz \
--cc=kirill@shutemov.name \
--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;
as well as URLs for NNTP newsgroup(s).