All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Max Filippov <jcmvbkbc@gmail.com>, Guenter Roeck <linux@roeck-us.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-xtensa@linux-xtensa.org" <linux-xtensa@linux-xtensa.org>
Subject: Re: next-20160804: Build error when building xtensa images
Date: Wed, 24 Aug 2016 22:02:26 +0530	[thread overview]
Message-ID: <57BDCC1A.6050505@gmail.com> (raw)
In-Reply-To: <CAMo8BfKpFqjSpqz44kZKDuTfFYFBdAQj=ko8Fy_iJjZEbXcE9w@mail.gmail.com>

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@roeck-us.net> 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

      reply	other threads:[~2016-08-24 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04  6:30 next-20160804: Build error when building xtensa images Guenter Roeck
2016-08-04 13:25 ` Max Filippov
2016-08-24 16:32   ` Sudip Mukherjee [this message]

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=57BDCC1A.6050505@gmail.com \
    --to=sudipm.mukherjee@gmail.com \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xtensa@linux-xtensa.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.