All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Prebuilt ARC tools are way too old
Date: Mon, 4 Feb 2019 09:25:48 +0100	[thread overview]
Message-ID: <20190204092548.15b42a23@windsurf> (raw)
In-Reply-To: <4881796E12491D4BB15146FE0209CE64681D2D2A@DE02WEMBXB.internal.synopsys.com>

Hello Alexey,

On Mon, 4 Feb 2019 08:13:11 +0000
Alexey Brodkin <alexey.brodkin@synopsys.com> wrote:

> May I kindly ask you to create a newer prebuilt ARC toolchain
> which uses arc-2018.09 GNU tools?
> 
> arc-2018.09 is based on GCC 8.2 and has a bunch of fixes as compared to
> older tools.
> 
> As of today the latest prebuilt ARC tools are br-arcle-hs38-full-2018.11-rc1.tar.bz2
> and it's still based on arc-2018.03 (GCC 7.x based).
> 
> What's more in ARC config fragment even older tarball is mentioned 
> https://git.buildroot.org/buildroot/tree/support/config-fragments/autobuild/br-arcle-hs38.config#n6
> 
> Probably there's not much sense in updating br-arcle-hs38.config with still obsolete
> tools and better wait before GCC 8.x based tools are available in prebuilt form.

Thanks for pinging me on this! I'll rebuild the toolchain with 2018.11
for now, and once 2019.02-rc1 is released, I'll rebuild again.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-02-04  8:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04  8:13 [Buildroot] Prebuilt ARC tools are way too old Alexey Brodkin
2019-02-04  8:25 ` Thomas Petazzoni [this message]
2019-02-04  8:27   ` Alexey Brodkin
2019-02-04  8:32     ` Thomas Petazzoni
2019-02-04  8:40       ` Alexey Brodkin

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=20190204092548.15b42a23@windsurf \
    --to=thomas.petazzoni@bootlin.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.