From: Nicholas Piggin <npiggin@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
PowerPC <linuxppc-dev@lists.ozlabs.org>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure in the powerpc allyesconfig build
Date: Mon, 5 Dec 2016 16:41:53 +1100 [thread overview]
Message-ID: <20161205164153.43c84010@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <20161205162431.71013317@canb.auug.org.au>
On Mon, 5 Dec 2016 16:24:31 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> On Mon, 5 Dec 2016 16:22:04 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > After mergeing everything but Andrew's tree, today's linux-next build
> > (powerpc allyesconfig) failed like this:
> >
> > kallsyms failure: relative symbol value 0xc000000000000000 out of range in relative mode
> >
> > I have no idea what caused this, so I have left the powerpc allyesconfig
> > build broken for now.
>
> Just as a data point, I tried reverting commit
>
> dadc4a1bb9f0 ("powerpc/64: Fix placement of .text to be immediately following .head.text")
>
> but that did not help.
In scripts/kallsyms.c, is there a table[i].sym string you can print?
next prev parent reply other threads:[~2016-12-05 5:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 5:22 linux-next: build failure in the powerpc allyesconfig build Stephen Rothwell
2016-12-05 5:24 ` Stephen Rothwell
2016-12-05 5:41 ` Nicholas Piggin [this message]
2016-12-05 6:16 ` Stephen Rothwell
2016-12-08 13:31 ` Arnd Bergmann
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=20161205164153.43c84010@roar.ozlabs.ibm.com \
--to=npiggin@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--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).