linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@linux.vnet.ibm.com>
To: Balbir Singh <bsingharora@gmail.com>
Cc: linux-next@vger.kernel.org,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linuxppc-dev@lists.ozlabs.org
Subject: Re: -next build failure with gcc 5.2.1
Date: Thu, 8 Dec 2016 11:57:25 +0530	[thread overview]
Message-ID: <5CF53903-E68A-42C5-93B9-767F417EE837@linux.vnet.ibm.com> (raw)
In-Reply-To: <798a8079-6d96-6a9c-b413-21e46f0fcbb0@gmail.com>


> On 08-Dec-2016, at 7:39 AM, Balbir Singh <bsingharora@gmail.com> wrote:
> 
> On 12/07/2016 07:26 PM, Sachin Sant wrote:
>> next tree fails to build on a ppc64le box with following message
>> 
>>  LD      init/built-in.o
>>  LD      vmlinux.o
>>  MODPOST vmlinux.o
>> WARNING: modpost: Found 3 section mismatch(es).
>> To see full details build your kernel with:
>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
>>  KSYM    .tmp_kallsyms1.o
>> kallsyms failure: relative symbol value 0xc000000000000000 out of range in relative mode
>> Makefile:969: recipe for target 'vmlinux' failed
>> make: *** [vmlinux] Error 1
>> 
>> GCC version is : gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
>> 
>> Have attached kernel config file.
>> 
> 
> Thanks, would you be in a position to bisect?

Yes. It seems Stephen has already found the commit causing this. 

Thanks
-Sachin

      reply	other threads:[~2016-12-08  6:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-07  8:26 -next build failure with gcc 5.2.1 Sachin Sant
2016-12-08  2:09 ` Balbir Singh
2016-12-08  6:27   ` Sachin Sant [this message]

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=5CF53903-E68A-42C5-93B9-767F417EE837@linux.vnet.ibm.com \
    --to=sachinp@linux.vnet.ibm.com \
    --cc=bsingharora@gmail.com \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=sfr@canb.auug.org.au \
    /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).