From: Guenter Roeck <linux@roeck-us.net>
To: Nick Krause <xerofoify@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Fwd: Allyesconfig for powerpc still Failing
Date: Mon, 07 Jul 2014 20:57:33 -0700 [thread overview]
Message-ID: <53BB6C2D.60209@roeck-us.net> (raw)
In-Reply-To: <CAPDOMVgeUWGtMC2yssh3zz6y208mHW5WCduDCwr+J09d7LF+CQ@mail.gmail.com>
On 07/07/2014 08:38 PM, Nick Krause wrote:
> 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....
>
> Guenter Roeck wrote on Mon, Jul 7, 2014 at 11:07 PM
> 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
>
> Hey Guenter,
> Would you mind sending me the patch that fixes these errors.
> I would like to test it before sending in to Ben.
> Cheers Nick
>
Hi Nick,
Just follow the link above, select 'forward', and follow the directions.
You'll get the patch per e-mail.
Alternative:
wget "http://download.gmane.org/gmane.linux.kernel/1736036/1736037"
The patch will be in a file named '1736037'.
I copied the list for others, in case the 'how to download a patch'
question comes up again.
Guenter
next prev parent reply other threads:[~2014-07-08 3:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-08 2:45 Allyesconfig for powerpc still Failing Nick Krause
2014-07-08 2:45 ` Nick Krause
2014-07-08 3:03 ` Benjamin Herrenschmidt
2014-07-08 3:03 ` Benjamin Herrenschmidt
2014-07-08 3:09 ` Nick Krause
2014-07-08 3:09 ` Nick Krause
2014-07-08 3:13 ` Fwd: " Nick Krause
2014-07-08 3:13 ` Nick Krause
2014-07-08 3:07 ` Guenter Roeck
2014-07-08 3:07 ` Guenter Roeck
[not found] ` <CAPDOMVgeUWGtMC2yssh3zz6y208mHW5WCduDCwr+J09d7LF+CQ@mail.gmail.com>
2014-07-08 3:57 ` Guenter Roeck [this message]
2014-07-08 4:57 ` Fwd: Fwd: " Nick Krause
2014-07-08 4:57 ` Nick Krause
[not found] ` <1404798135.16156.50.camel@pasglop>
2014-07-12 3:13 ` Nick Krause
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=53BB6C2D.60209@roeck-us.net \
--to=linux@roeck-us.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.