linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, Kees Cook <keescook@chromium.org>,
	Emese Revfy <re.emese@gmail.com>,
	kernel-hardening@lists.openwall.com
Subject: Re: linux-next: Tree for Jun 9
Date: Thu, 09 Jun 2016 23:06:41 +0100	[thread overview]
Message-ID: <5759E871.3040706@gmail.com> (raw)
In-Reply-To: <20160609163408.37fb77b9@canb.auug.org.au>

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.


Regards
Sudip

  reply	other threads:[~2016-06-09 22:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-09  6:34 Stephen Rothwell
2016-06-09 22:06 ` Sudip Mukherjee [this message]
2016-06-09 22:14   ` Kees Cook
2016-06-11  1:05     ` Paul Gortmaker
  -- strict thread matches above, loose matches on Subject: below --
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=5759E871.3040706@gmail.com \
    --to=sudipm.mukherjee@gmail.com \
    --cc=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 \
    --subject='Re: linux-next: Tree for Jun 9' \
    /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

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).