Re: Linux kernel cross-compilers
From: Guenter Roeck
Date: Fri Aug 16 2013 - 05:21:22 EST
On 08/16/2013 01:31 AM, Max Filippov wrote:
On Fri, Aug 16, 2013 at 11:50 AM, Guenter Roeck <linux@xxxxxxxxxxxx> wrote:
On 08/16/2013 12:22 AM, Max Filippov wrote:
On Fri, Aug 16, 2013 at 9:48 AM, Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/