linux-snps-arc.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alexey.Brodkin@synopsys.com (Alexey Brodkin)
To: linux-snps-arc@lists.infradead.org
Subject: Build failure in linux mainline when building arcv2 images
Date: Mon, 1 Aug 2016 09:53:47 +0000	[thread overview]
Message-ID: <1470045132.28725.39.camel@synopsys.com> (raw)
In-Reply-To: <579C2C9E.6040904@roeck-us.net>

Hi Vineet,?Guenter,

On Fri, 2016-07-29@21:27 -0700, Guenter Roeck wrote:
> On 07/29/2016 03:46 PM, Vineet Gupta wrote:
> 
> > 
> > What you want is
> > 2016-05-19 09439560b9f9 toolchain: bump ARC tools to arc-2016.03 release
> > 
> > which seems to be present in released 2016.05, but when I checkout 2016.05 tag (or
> > aa6fd11feebff) that patch is not there !
> > 
> 
> A toolchain build off SHA 09439560b9f9 works.

Indeed we were a little-bit too late for BR 2016.05 release with
our toolchain bump so the patch in question only made its way in BR repo
right after BR release.

Anyways good to know your issue is resolved now.

Note with arc-2016.03 we still see a lot of issues here and there
because that's the first version that uses our rewritten from scratch binutils
(the base for binutils port upstreaming for ARC). And so in BR we continue to
update ARC tools to so-called engineering builds of our current development
branches of gcc and binutils. That information might be useful if you face any
other issues building stuff for ARC.

Or don't hesitate to email us so we'll try to point you to something that
should work :)

-Alexey

      reply	other threads:[~2016-08-01  9:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-29  3:23 Build failure in linux mainline when building arcv2 images Guenter Roeck
2016-07-29  5:20 ` Vineet Gupta
2016-07-29 13:43   ` Guenter Roeck
2016-07-29 20:03     ` Vineet Gupta
2016-07-29 21:48       ` Guenter Roeck
2016-07-29 22:46         ` Vineet Gupta
2016-07-30  4:27           ` Guenter Roeck
2016-08-01  9:53             ` Alexey Brodkin [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=1470045132.28725.39.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).