From: Kees Cook <keescook@chromium.org>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next <linux-next@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Emese Revfy <re.emese@gmail.com>,
"kernel-hardening@lists.openwall.com"
<kernel-hardening@lists.openwall.com>
Subject: Re: linux-next: Tree for Jun 9
Date: Thu, 9 Jun 2016 15:14:50 -0700 [thread overview]
Message-ID: <CAGXu5jJbzUueFvrBJvP3qhprKQ95fZqfgo08VvyG5HETL0a4Sw@mail.gmail.com> (raw)
In-Reply-To: <5759E871.3040706@gmail.com>
On Thu, Jun 9, 2016 at 3:06 PM, Sudip Mukherjee
<sudipm.mukherjee@gmail.com> wrote:
> On Thursday 09 June 2016 07:34 AM, Stephen Rothwell wrote:
>>
>> Hi all,
>>
>> News: there will be no linux-next releases on Friday (tomorrow) or
>> Monday, so the next release will be next-20160614 on Tuesday.
>>
>> Changes since 20160608:
>
>
> While trying to build x86_64 allmodconfig I am getting:
> ++ 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
>
> build log is at:
> https://travis-ci.org/sudipm-mukherjee/parport/jobs/136350824
>
> Looks like 6b90bd4ba40b ("GCC plugin infrastructure") is the problem.
Hi, yes, if you want to be testing the GCC plugins, you'll need the
gcc plugin headers installed. On Debian and Ubuntu, they can be found
like this:
$ apt-cache search gcc | grep plugin-dev
gcc-5-plugin-dev - Files for GNU GCC plugin development.
gcc-4.7-plugin-dev - Files for GNU GCC plugin development.
gcc-4.8-plugin-dev - Files for GNU GCC plugin development.
gcc-4.9-plugin-dev - Files for GNU GCC plugin development.
-Kees
--
Kees Cook
Chrome OS & Brillo Security
next prev parent reply other threads:[~2016-06-09 22:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 6:34 linux-next: Tree for Jun 9 Stephen Rothwell
2016-06-09 22:06 ` Sudip Mukherjee
2016-06-09 22:14 ` Kees Cook [this message]
2016-06-11 1:05 ` Paul Gortmaker
-- strict thread matches above, loose matches on Subject: below --
2023-06-09 4:06 Stephen Rothwell
2023-06-11 9:30 ` Stephen Rothwell
2022-06-09 4:13 Stephen Rothwell
2021-06-09 12:57 Stephen Rothwell
2020-06-09 12:59 Stephen Rothwell
2017-06-09 6:42 Stephen Rothwell
2017-06-09 13:58 ` Sumit Semwal
2015-06-09 14:44 Stephen Rothwell
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=CAGXu5jJbzUueFvrBJvP3qhprKQ95fZqfgo08VvyG5HETL0a4Sw@mail.gmail.com \
--to=keescook@chromium.org \
--cc=kernel-hardening@lists.openwall.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=re.emese@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=sudipm.mukherjee@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;
as well as URLs for NNTP newsgroup(s).