gcc-plugins: disable under COMPILE_TEST

Since adding the gcc plugin development headers is required for the
gcc plugin support, we should ease into this new kernel build dependency
more slowly. For now, disable the gcc plugins under COMPILE_TEST so that
all*config builds will skip it.

Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Michal Marek <mmarek@suse.com>

2 files changed, 3 insertions, 2 deletions

diff --git a/arch/Kconfig b/arch/Kconfig
index 05f1e95b796d..cae4bc587eae 100644
--- a/arch/Kconfig
+++ b/arch/Kconfig
@@ -366,6 +366,7 @@ config HAVE_GCC_PLUGINS
 menuconfig GCC_PLUGINS
         bool "GCC plugins"
         depends on HAVE_GCC_PLUGINS
+        depends on !COMPILE_TEST
         help
           GCC plugins are loadable modules that provide extra features to the
           compiler. They are useful for runtime instrumentation and static analysis.
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index b7827dca3fec..7936e5e4da9d 100644
--- a/lib/Kconfig.debug
+++ b/lib/Kconfig.debug
@@ -708,8 +708,8 @@ config KCOV
         bool "Code coverage for fuzzing"
         depends on ARCH_HAS_KCOV
         select DEBUG_FS
-        select GCC_PLUGINS
-        select GCC_PLUGIN_SANCOV
+        select GCC_PLUGINS if !COMPILE_TEST
+        select GCC_PLUGIN_SANCOV if !COMPILE_TEST
         help
           KCOV exposes kernel code coverage information in a form suitable
           for coverage-guided fuzzing (randomized testing).