Re: next-20160804: Build error when building xtensa images

From: Sudip Mukherjee
Date: Wed Aug 24 2016 - 12:32:43 EST


On Thursday 04 August 2016 06:55 PM, Max Filippov wrote:
Hi Guenter,

On Thu, Aug 4, 2016 at 9:30 AM, Guenter Roeck <linux@xxxxxxxxxxxx> wrote:
Hi Max,

I see the following build errors when building xtensa images in
next-20160804.

Error log:
arch/xtensa/kernel/built-in.o: In function `fast_alloca':
(.text+0x99a): dangerous relocation: j: cannot encode: _WindowUnderflow12
arch/xtensa/kernel/built-in.o: In function `fast_alloca':
(.text+0x99d): dangerous relocation: j: cannot encode: _WindowUnderflow8
arch/xtensa/kernel/built-in.o: In function `fast_alloca':
(.text+0x9a0): dangerous relocation: j: cannot encode: _WindowUnderflow4
arch/xtensa/kernel/built-in.o: In function
`window_overflow_restore_a0_fixup':
(.text+0x23a3): dangerous relocation: j: cannot encode:
(.DoubleExceptionVector.text+0x104)
arch/xtensa/kernel/built-in.o: In function
`window_overflow_restore_a0_fixup':
(.text+0x23c1): dangerous relocation: j: cannot encode:
(.DoubleExceptionVector.text+0x104)
arch/xtensa/kernel/built-in.o: In function
`window_overflow_restore_a0_fixup':
(.text+0x23dd): dangerous relocation: j: cannot encode:
(.DoubleExceptionVector.text+0x104)

This affects all images I am testing.

Bisect points to 'xtensa: cleanup MMU setup and kernel layout macros'.

Thanks for the report. The default kernel load address in this patch
was wrong. Fix posted.

xtensa builds still fails with that same error.
Did the fix make its way to linux-next?

xtensa defconfig for next-20160824 is at:
https://travis-ci.org/sudipm-mukherjee/parport/jobs/154646688

regards
sudip