From: Kees Cook <keescook@chromium.org>
To: "H. Nikolaus Schaller" <hns@goldelico.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Discussions about the Letux Kernel
<letux-kernel@openphoenux.org>
Subject: Re: [BUG v5.2-rc1] ARM build broken
Date: Mon, 20 May 2019 08:59:50 -0700 [thread overview]
Message-ID: <201905200855.391A921AB@keescook> (raw)
In-Reply-To: <4DB08A04-D03A-4441-85DE-64A13E6D709C@goldelico.com>
On Mon, May 20, 2019 at 05:15:02PM +0200, H. Nikolaus Schaller wrote:
> Hi,
> it seems as if ARM build is broken since ARM now hard enables CONFIG_HAVE_GCC_PLUGINS
> which indirectly enables CONFIG_GCC_PLUGIN_ARM_SSP_PER_TASK. Compiling this breaks
> on my system (Darwin build host) due to conflicts in system headers and Linux headers.
>
> So how can I turn off all these GCC_PLUGINS?
>
> The offending patch seems to be
>
> security: Create "kernel hardening" config area
>
> especially the new "default y" for GCC_PLUGINS. After removing that line from
> scripts/gcc-plugins/Kconfig makes my compile succeed.
The intention is to enable it _if_ the plugins are available as part of
the build environment. The "default y" on GCC_PLUGINS is mediated by:
depends on HAVE_GCC_PLUGINS
depends on PLUGIN_HOSTCC != ""
So it seems that something isn't working in the plugin detection maybe?
Can you send your build error, compiler version, .config, etc? I've not
been able to reproduce this problem. (And I'm not aware of any of the
automated build systems failing in this area yet either...) Perhaps it's
something specific to building under Darwin?
Thanks!
--
Kees Cook
next parent reply other threads:[~2019-05-20 15:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DB08A04-D03A-4441-85DE-64A13E6D709C@goldelico.com>
2019-05-20 15:59 ` Kees Cook [this message]
[not found] ` <D8F987B2-8F41-46DE-B298-89541D7A9774@goldelico.com>
2019-05-20 18:53 ` [BUG v5.2-rc1] ARM build broken Kees Cook
2019-05-20 19:35 ` H. Nikolaus Schaller
2019-05-20 20:25 ` Kees Cook
2019-05-20 21:21 ` Chris Packham
2019-05-21 11:23 ` H. Nikolaus Schaller
2019-05-21 20:36 ` Kees Cook
2019-05-22 6:02 ` H. Nikolaus Schaller
2019-06-03 7:46 ` [Letux-kernel] " H. Nikolaus Schaller
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=201905200855.391A921AB@keescook \
--to=keescook@chromium.org \
--cc=hns@goldelico.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yamada.masahiro@socionext.com \
/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