From: Julia Lawall <julia.lawall@lip6.fr>
To: re.emese@gmail.com, keescook@chromium.org
Cc: linux-kernel@vger.kernel.org
Subject: compilation with plugins
Date: Sat, 11 Jun 2016 20:29:32 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.02.1606112024230.2055@localhost6.localdomain6> (raw)
Hello,
I am not able to compile anything with last Friday's linux-next:
commit 8f6027f7e808ed7c1fd8c8d37fc7a5076c683c4f
Author: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Thu Jun 9 16:31:36 2016 +1000
After running make allyesconfig, I get the following when trying to
compile any file:
cripts/Makefile.gcc-plugins:17: warning: cannot use CONFIG_KCOV:
-fsanitize-coverage=trace-pc is not supported by compiler
++ dirname ./scripts/gcc-plugin.sh
+ srctree=./scripts
++ gcc -print-file-name=plugin
+ gccplugins_dir=plugin
++ g++ -E -x c++ - -o /dev/null -I./scripts/gcc-plugins -Iplugin/include
+ plugincc='In file included from <stdin>:1:0:
./scripts/gcc-plugins/gcc-common.h:4:22: fatal error: bversion.h: No such
file or directory
#include "bversion.h"
^
compilation terminated.'
+ '[' 1 -ne 0 ']'
+ exit 1
scripts/Makefile.gcc-plugins:30: warning: your gcc installation does not
support plugins, perhaps the necessary headers are missing?
CHK include/config/kernel.release
CHK include/generated/uapi/linux/version.h
CHK include/generated/utsrelease.h
HOSTCXX -fPIC scripts/gcc-plugins/sancov_plugin.o
In file included from scripts/gcc-plugins/sancov_plugin.c:22:0:
scripts/gcc-plugins/gcc-common.h:4:22: fatal error: bversion.h: No such
file or directory
#include "bversion.h"
^
compilation terminated.
make[1]: *** [scripts/gcc-plugins/sancov_plugin.o] Error 1
make: *** [gcc-plugins] Error 2
-------------------
gcc --version gives:
gcc (Ubuntu 4.8.4-2ubuntu1~14.04.3) 4.8.4
Is there some way to disable the use of plugins, or to solve the problem
in some other way?
thanks,
julia
next reply other threads:[~2016-06-11 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-11 18:29 Julia Lawall [this message]
2016-06-11 18:57 ` Kees Cook
2016-06-11 19:02 ` Julia Lawall
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=alpine.DEB.2.02.1606112024230.2055@localhost6.localdomain6 \
--to=julia.lawall@lip6.fr \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=re.emese@gmail.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
all inboxes | Powered by JetHome®