All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <alexey.brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [arc-buildroot] [PATCH] toolchain: Bump ARC tools to arc-2018.09-rc1
Date: Thu, 15 Nov 2018 03:51:49 +0000	[thread overview]
Message-ID: <a4c4c371bc8fbefc5e3e1a466ed80dfd334a4b9a.camel@synopsys.com> (raw)
In-Reply-To: <20181108113207.40589-1-Evgeniy.Didin@synopsys.com>

Hi Thomas, Peter, Arnout!

On Thu, 2018-11-08 at 14:32 +0300, Evgeniy Didin wrote:
> This commit bumps ARC toolchain to arc-2018.09-rc1.
> We want to test how new toolchain-rc1 builds packages,
> so we can make fixes before release of toolcain.
> 
> ARC GNU tools of version arc-2018.09-rc1 bring some quite significant changes like:
> * Binutils v2.31.1 with additional ARC patches
> * GCC 8.2.1 with additional ARC patches
> * glibc 2.28 with additional ARC patches
> 
> Please note that it is a release candidate and it might contain some
> breakages, please don't use it for production builds.
> 
> Signed-off-by: Evgeniy Didin <didin@synopsys.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> Cc: arc-buildroot at synopsys.com

Any chance arc-2018.09 tools to be accepted in v2018.11 BR release?

In the meantime we've got RC2 cut just yesterday with a couple of more
critical fixes so it might make sense to bump right to arc-2018.09-rc2
instead but still it might be applied on top of this one so pls let us
know what would you prefer.

-Alexey

  reply	other threads:[~2018-11-15  3:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-08 11:32 [Buildroot] [PATCH] toolchain: Bump ARC tools to arc-2018.09-rc1 Evgeniy Didin
2018-11-15  3:51 ` Alexey Brodkin [this message]
2018-11-18 19:50   ` [Buildroot] [arc-buildroot] " Peter Korsgaard
2018-11-19  8:14     ` Alexey Brodkin
2018-11-19  9:46       ` Peter Korsgaard

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=a4c4c371bc8fbefc5e3e1a466ed80dfd334a4b9a.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.com \
    --cc=buildroot@busybox.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.