[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNAQNbV1afjkoKfgvjijkhkQN3-8or8Aq7Mm9X2xiemiXrw@mail.gmail.com>
Date: Thu, 12 Jul 2018 19:03:16 +0900
From: Masahiro Yamada <yamada.masahiro@...ionext.com>
To: Laura Abbott <labbott@...hat.com>
Cc: Josh Poimboeuf <jpoimboe@...hat.com>, Jiri Olsa <jolsa@...nel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Robin Jarry <robin.jarry@...nd.com>
Subject: Re: [PATCHv2] treewide: Rename HOSTCFLAGS -> KBUILD_HOSTCFLAGS
Hi.
2018-07-10 9:45 GMT+09:00 Laura Abbott <labbott@...hat.com>:
> In preparation for enabling command line CFLAGS, re-name HOSTCFLAGS to
> KBUILD_HOSTCFLAGS as the internal use only flags. This should not have any
> visible effects.
>
> Signed-off-by: Laura Abbott <labbott@...hat.com>
> ---
> v2: Dropped name change for individual files (still CHOSTFLAGS_foo)
> ---
One more fix for a document.
diff --git a/Documentation/kbuild/makefiles.txt
b/Documentation/kbuild/makefiles.txt
index 048fc39..63655c1 100644
--- a/Documentation/kbuild/makefiles.txt
+++ b/Documentation/kbuild/makefiles.txt
@@ -661,7 +661,7 @@ Both possibilities are described in the following.
When compiling host programs, it is possible to set specific flags.
The programs will always be compiled utilising $(HOSTCC) passed
- the options specified in $(HOSTCFLAGS).
+ the options specified in $(KBUILD_HOSTCFLAGS).
To set flags that will take effect for all host programs created
in that Makefile, use the variable HOST_EXTRACFLAGS.
I will fold this.
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists