From: Max Filippov <jcmvbkbc@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Linux kernel cross-compilers
Date: Fri, 16 Aug 2013 12:31:59 +0400 [thread overview]
Message-ID: <CAMo8BfLvVk+2CyQD28otU265J4rvbt0Eg11Vqr4u4zjKjrTanw@mail.gmail.com> (raw)
In-Reply-To: <520DD9CA.90305@roeck-us.net>
On Fri, Aug 16, 2013 at 11:50 AM, Guenter Roeck <linux@roeck-us.net> wrote:
> On 08/16/2013 12:22 AM, Max Filippov wrote:
>>
>> On Fri, Aug 16, 2013 at 9:48 AM, Tony Breeds <tony@bakeyournoodle.com>
>> wrote:
>>>
>>> On Thu, Aug 15, 2013 at 01:46:16PM +0400, Max Filippov wrote:
>>>
>>>> Yes, xtensa compiler/linker is known to have issues with link-time
>>>> relaxation; e.g. it may fail to build linux image without
>>>> CONFIG_LD_NO_RELAX.
>>>
>>>
>>> Is there something I can do at linker build time to help with this?
>>
>>
>> I don't think so. Apparently it's not a linker configuration issue, it's a
>> bug.
>>
> CONFIG_LD_NO_RELAX doesn't help.
>
> For reference, here is the error:
>
> xtensa-linux-objcopy: Unable to change endianness of input file(s)
> make[2]: *** [arch/xtensa/boot/boot-elf/Image.o] Error 1
> make[1]: *** [boot-elf] Error 2
> make: *** [zImage] Error 2
>
> Oddly enough, I only see the problem on one of three servers.
Guenter,
can you share a complete build log with V=1?
--
Thanks.
-- Max
next prev parent reply other threads:[~2013-08-16 8:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 9:07 Linux kernel cross-compilers Guenter Roeck
2013-08-15 9:46 ` Max Filippov
2013-08-15 14:02 ` Guenter Roeck
2013-08-15 14:22 ` Max Filippov
2013-08-15 14:34 ` Guenter Roeck
2013-08-16 5:48 ` Tony Breeds
2013-08-16 7:22 ` Max Filippov
2013-08-16 7:50 ` Guenter Roeck
2013-08-16 8:31 ` Max Filippov [this message]
2013-08-16 9:21 ` Guenter Roeck
2013-08-16 9:45 ` Max Filippov
2013-08-16 15:43 ` Guenter Roeck
2013-08-16 19:09 ` Max Filippov
2013-08-17 16:56 ` Sam Ravnborg
2013-08-16 19:26 ` Sam Ravnborg
2013-08-16 20:19 ` Guenter Roeck
2013-08-16 5:47 ` Tony Breeds
2013-08-16 7:54 ` Guenter Roeck
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=CAMo8BfLvVk+2CyQD28otU265J4rvbt0Eg11Vqr4u4zjKjrTanw@mail.gmail.com \
--to=jcmvbkbc@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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.