From: Michal Marek <mmarek@suse.com>
To: RaphaelWu@viatech.com.cn
Cc: linux-kbuild@vger.kernel.org
Subject: Re: how to echo $(KBUILD_CFLAGS)
Date: Thu, 20 Aug 2015 12:49:50 +0200 [thread overview]
Message-ID: <55D5B0CE.1040900@suse.com> (raw)
In-Reply-To: <848BD1798F19584EADB3CD55379CFD64665E59C7@SHMX01.s3graphics.com>
On 2015-08-20 12:45, RaphaelWu@viatech.com.cn wrote:
> Hi,
>
> I have seen this VAR used in some kernel module which also forbid ftrace.
> but I was curious about whenever I echo $(KBUILD_CFLAGS), it's always empty.
>
> all:
> @echo $(KBUILD_CFLAGS)
> $(MAKE) -C /path-of-kernel/ M=$(PWD) modules
This does not look like a kbuild makefile, so it does not see any
KBUILD_* variables.
Michal
next prev parent reply other threads:[~2015-08-20 10:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-20 10:45 how to echo $(KBUILD_CFLAGS) RaphaelWu
2015-08-20 10:49 ` Michal Marek [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-08-21 1:08 RaphaelWu
2015-08-20 12:04 RaphaelWu
2015-08-20 11:03 RaphaelWu
2015-08-20 11:34 ` Michal Marek
2015-08-20 17:19 ` Sam Ravnborg
2015-08-20 2:03 RaphaelWu
2015-08-20 8:57 ` Michal Marek
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=55D5B0CE.1040900@suse.com \
--to=mmarek@suse.com \
--cc=RaphaelWu@viatech.com.cn \
--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).