From: Josh Poimboeuf <jpoimboe@redhat.com>
To: Jiri Slaby <jslaby@suse.cz>
Cc: Jiri Olsa <jolsa@redhat.com>, Michal Marek <MMarek@suse.com>,
linux-kbuild@vger.kernel.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Kbuild: CC= handling broken for tools/
Date: Fri, 11 Nov 2016 11:21:16 -0600 [thread overview]
Message-ID: <20161111172116.2kti4pdkqu6bjpvy@treble> (raw)
In-Reply-To: <fb1c54e7-be4d-ba9b-cb2a-1b80c9ce1377@suse.cz>
On Fri, Nov 11, 2016 at 06:08:24PM +0100, Jiri Slaby wrote:
> On 11/11/2016, 04:30 PM, Josh Poimboeuf wrote:
> > Does it work if you use KCFLAGS instead of EXTRA_CFLAGS?
>
> Yes, the kernel builds with the flags now.
>
> But objtool is unexpectedly still built by a different compiler.
>
> I would also prefer the flags (like the warning above) to be passed even
> when building host commands.
In that case, if you want to build *everything* in tools and kernel with
the new compiler and new flags, I think you'll need to set HOSTCC,
HOSTCFLAGS, and CFLAGS, in addition to CC and KCFLAGS.
objtool uses the host compiler, but it doesn't support setting HOSTCC or
HOSTCFLAGS yet. It always just uses 'gcc'. I'll add HOSTCC/HOSTCFLAGS
to the TODO list, though feel free to work up a patch.
--
Josh
prev parent reply other threads:[~2016-11-11 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-11 11:23 Kbuild: CC= handling broken for tools/ Jiri Slaby
2016-11-11 12:38 ` Michal Marek
2016-11-11 14:00 ` Jiri Olsa
2016-11-11 14:04 ` Jiri Slaby
2016-11-11 15:14 ` Jiri Olsa
2016-11-11 15:30 ` Josh Poimboeuf
2016-11-11 17:08 ` Jiri Slaby
2016-11-11 17:21 ` Josh Poimboeuf [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=20161111172116.2kti4pdkqu6bjpvy@treble \
--to=jpoimboe@redhat.com \
--cc=MMarek@suse.com \
--cc=jolsa@redhat.com \
--cc=jslaby@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@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