From: kbuild test robot <fengguang.wu@intel.com>
To: Emese Revfy <re.emese@gmail.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Michal Marek <mmarek@suse.com>
Subject: scripts/gcc-plugins/gcc-common.h:4:22: fatal error: bversion.h: No such file or directory
Date: Sun, 6 Nov 2016 07:09:57 +0800 [thread overview]
Message-ID: <201611060755.pjWd66YC%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2819 bytes --]
Hi Emese,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: ffbcbfca846ed117e3d4009acfbf1e1590c56b2f
commit: 543c37cb165049c3be24a0d4733e67caa2b33eef Add sancov plugin
date: 5 months ago
config: x86_64-randconfig-in0-11060649 (attached as .config)
compiler: gcc-4.6 (Debian 4.6.4-7) 4.6.4
reproduce:
git checkout 543c37cb165049c3be24a0d4733e67caa2b33eef
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
scripts/Makefile.gcc-plugins:17: warning: cannot use CONFIG_KCOV: -fsanitize-coverage=trace-pc is not supported by compiler
++(scripts/gcc-plugin.sh:2): main(): dirname scripts/gcc-plugin.sh
+(scripts/gcc-plugin.sh:2): main(): srctree=scripts
++(scripts/gcc-plugin.sh:3): main(): gcc-4.6 -print-file-name=plugin
+(scripts/gcc-plugin.sh:3): main(): gccplugins_dir=plugin
++(scripts/gcc-plugin.sh:12): main(): gcc-4.6 -E -x c++ - -o /dev/null -Iscripts/gcc-plugins -Iplugin/include
+(scripts/gcc-plugin.sh:12): main(): 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
compilation terminated.'
+(scripts/gcc-plugin.sh:14): main(): '[' 1 -ne 0 ']'
+(scripts/gcc-plugin.sh:16): main(): exit 1
scripts/Makefile.gcc-plugins:30: warning: your gcc installation does not support plugins, perhaps the necessary headers are missing?
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[2]: *** [scripts/gcc-plugins/sancov_plugin.o] Error 1
make[2]: Target '__build' not remade because of errors.
make[1]: *** [gcc-plugins] Error 2
make[1]: Target 'prepare' not remade because of errors.
make: *** [sub-make] Error 2
vim +4 scripts/gcc-plugins/gcc-common.h
6b90bd4b Emese Revfy 2016-05-24 1 #ifndef GCC_COMMON_H_INCLUDED
6b90bd4b Emese Revfy 2016-05-24 2 #define GCC_COMMON_H_INCLUDED
6b90bd4b Emese Revfy 2016-05-24 3
6b90bd4b Emese Revfy 2016-05-24 @4 #include "bversion.h"
6b90bd4b Emese Revfy 2016-05-24 5 #if BUILDING_GCC_VERSION >= 6000
6b90bd4b Emese Revfy 2016-05-24 6 #include "gcc-plugin.h"
6b90bd4b Emese Revfy 2016-05-24 7 #else
:::::: The code at line 4 was first introduced by commit
:::::: 6b90bd4ba40b38dc13c2782469c1c77e4ed79915 GCC plugin infrastructure
:::::: TO: Emese Revfy <re.emese@gmail.com>
:::::: CC: Michal Marek <mmarek@suse.com>
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 27527 bytes --]
next reply other threads:[~2016-11-05 23:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-05 23:09 kbuild test robot [this message]
2016-11-06 8:19 ` Emese Revfy
2016-11-08 2:25 ` Fengguang Wu
2017-02-05 1:55 kbuild test robot
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=201611060755.pjWd66YC%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.com \
--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
Powered by JetHome