mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Linux kernel cross-compilers
Date: Fri, 16 Aug 2013 02:21:09 -0700	[thread overview]
Message-ID: <520DEF05.9030803@roeck-us.net> (raw)
In-Reply-To: <CAMo8BfLvVk+2CyQD28otU265J4rvbt0Eg11Vqr4u4zjKjrTanw@mail.gmail.com>

On 08/16/2013 01:31 AM, Max Filippov wrote:
> 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?
>

http://roeck-us.net/linux/logs/make.xtensa.log.bad
http://roeck-us.net/linux/logs/make.xtensa.log.ok

Key difference: the failing command in the bad case is
	xtensa-linux-objcopy -O elf32-xtensa-le
and in the good case
	xtensa-linux-objcopy -O elf32-xtensa-be

Same compiler (4.6.3 from kernel.org), same configuration file, same command line.
Configuration file is generated from defconfig, and the resulting .config file
is the same in both cases.

If I execute make and expicitly set BIG_ENDIAN=1 on the failing system as parameter to it,
it works fine. If I set BIG_ENDIAN=0 on the passing system, it fails.

I am puzzled. Guess there must be something different, but I have no idea what it might be.

If I execute the command which sets BIG_ENDIAN manually from the shell (from
arch/xtensa/boot/Makefile), it returns 1 on both systems.

If you have an idea what is going on please let me know.

Thanks,
Guenter


  reply	other threads:[~2013-08-16  9:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15  9:07 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
2013-08-16  9:21           ` Guenter Roeck [this message]
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=520DEF05.9030803@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

Powered by JetHome