From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: kisskb: FAILED linux-next/axs103_smp_defconfig/arcv2 Thu Jun 09, 17:31
Date: Thu, 9 Jun 2016 08:44:02 +0000 [thread overview]
Message-ID: <1465461796.3203.25.camel@synopsys.com> (raw)
In-Reply-To: <57592981.2060604@synopsys.com>
Hi Michael,
On Thu, 2016-06-09@14:02 +0530, Vineet Gupta wrote:
> Hi Michael,
>
> On Thursday 09 June 2016 01:02 PM, noreply@ellerman.id.au wrote:
> >
> > FAILED linux-next/axs103_smp_defconfig/arcv2 Thu Jun 09, 17:31
> >
> > http://kisskb.ellerman.id.au/kisskb/buildresult/12713783/
> >
> > Commit:???Add linux-next specific files for 20160609
> > ??????????8f6027f7e808ed7c1fd8c8d37fc7a5076c683c4f
> > Compiler: arc-buildroot-linux-uclibc-gcc (Buildroot 2015.08.1) 4.8.4
> >
> > Possible errors
> > ---------------
> >
> > {standard input}:18606: Error: Instruction with long immediate data in delay slot
> > make[2]: *** [block/cfq-iosched.o] Error 1
> > make[1]: *** [block] Error 2
> > make: *** [sub-make] Error 2
> This problem has been fixed in tools since - can you switch to a newer toolchain -
> such as one released last month. @Alexey can you point Michael to right buildroot
> version ?
Unfortunately our most recent tools were released a little bit too late to get in
the most recent Buildroot version and so you'll need to build your toolchain
from Buildroot's master branch. Basically everything after the following commit will
should work:?https://git.busybox.net/buildroot/commit/?id=caf515e25e699eb306d0b24986734790de80af28
-Alexey
next prev parent reply other threads:[~2016-06-09 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 7:32 kisskb: FAILED linux-next/axs103_smp_defconfig/arcv2 Thu Jun 09, 17:31 noreply
2016-06-09 8:32 ` Vineet Gupta
2016-06-09 8:44 ` Alexey Brodkin [this message]
2016-06-09 11:29 ` Michael Ellerman
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=1465461796.3203.25.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=linux-snps-arc@lists.infradead.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 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.