From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nick Krause <xerofoify@gmail.com>
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: Tue, 08 Jul 2014 13:03:54 +1000 [thread overview]
Message-ID: <1404788634.16156.38.camel@pasglop> (raw)
In-Reply-To: <CAPDOMVi5ptjaKzT+Exd3XtKcy7W7nNZYUD+MEwN8LmhPrQTZBQ@mail.gmail.com>
On Mon, 2014-07-07 at 22:45 -0400, 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....
Yes, it's a trainwreck and I don't know how to fix it yet ... I tried
various more or less invasive approaches and none of them worked
properly so far. I need to spend more time on this.
Cheers,
Ben.
next prev parent reply other threads:[~2014-07-08 3:04 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 [this message]
2014-07-08 3:09 ` Nick Krause
2014-07-08 3:13 ` Fwd: " Nick Krause
2014-07-08 3:07 ` Guenter Roeck
[not found] ` <CAPDOMVgeUWGtMC2yssh3zz6y208mHW5WCduDCwr+J09d7LF+CQ@mail.gmail.com>
2014-07-08 3:57 ` Fwd: " 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=1404788634.16156.38.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.vnet.ibm.com \
--cc=michael@ellerman.id.au \
--cc=paulus@samba.org \
--cc=xerofoify@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).