From: Guenter Roeck <linux@roeck-us•net>
To: Nick Krause <xerofoify@gmail•com>, benh@kernel•crashing.org
Cc: mahesh@linux•vnet.ibm.com, agraf@suse•de,
"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
michael@ellerman•id.au, paulus@samba•org, anton@samba•org,
linuxppc-dev@lists•ozlabs.org
Subject: Re: Allyesconfig for powerpc still Failing
Date: Mon, 07 Jul 2014 20:07:19 -0700 [thread overview]
Message-ID: <53BB6067.1090402@roeck-us.net> (raw)
In-Reply-To: <CAPDOMVi5ptjaKzT+Exd3XtKcy7W7nNZYUD+MEwN8LmhPrQTZBQ@mail.gmail.com>
On 07/07/2014 07:45 PM, Nick Krause wrote:
> Today I tested the allyesconfig for powerpc and it seems to be still
> failing according to my tests.
> Below are the error messages I get before the jobs finish and exit
> failing the build.
> Cheers Nick
> arch/powerpc/kernel/exceptions-64s.S: Assembler messages:
> arch/powerpc/kernel/exceptions-64s.S:1331: Error: attempt to move .org backwards
> make[1]: *** [arch/powerpc/kernel/head_64.o] Error 1
> make: *** [arch/powerpc/kernel] Error 2
> make: *** Waiting for unfinished jobs....
I submitted a patch to work around this problem a couple of weeks ago [1].
Unfortunately, with this patch applied, allyesconfig still fails with
relocation errors, but at least the above message is gone, and
allmodconfig passes.
Maybe we can convince Ben to accept the patch ...
Thanks,
Guenter
---
[1] https://lkml.org/lkml/2014/6/30/607
next prev parent reply other threads:[~2014-07-08 3:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 2:45 Allyesconfig for powerpc still Failing Nick Krause
2014-07-08 3:03 ` Benjamin Herrenschmidt
2014-07-08 3:09 ` Nick Krause
2014-07-08 3:13 ` Fwd: " Nick Krause
2014-07-08 3:07 ` Guenter Roeck [this message]
[not found] ` <CAPDOMVgeUWGtMC2yssh3zz6y208mHW5WCduDCwr+J09d7LF+CQ@mail.gmail.com>
2014-07-08 3:57 ` Guenter Roeck
2014-07-08 4:57 ` Fwd: " Nick Krause
[not found] ` <1404798135.16156.50.camel@pasglop>
2014-07-12 3:13 ` Nick Krause
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=53BB6067.1090402@roeck-us.net \
--to=linux@roeck-us$(echo .)net \
--cc=agraf@suse$(echo .)de \
--cc=anton@samba$(echo .)org \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mahesh@linux$(echo .)vnet.ibm.com \
--cc=michael@ellerman$(echo .)id.au \
--cc=paulus@samba$(echo .)org \
--cc=xerofoify@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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