Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] extern-toolchain: Bump ARC tools to arc-2017.09-rc1
Date: Wed, 11 Oct 2017 20:51:47 +0000	[thread overview]
Message-ID: <1507755106.3839.19.camel@synopsys.com> (raw)
In-Reply-To: <275d998b-73cf-ebd0-2047-a48704eeda36@mind.be>

Hi Arnout,

On Wed, 2017-10-11 at 22:14 +0200, Arnout Vandecappelle wrote:
> 
> On 11-10-17 11:17, Evgeniy Didin wrote:
> > 
> > This commit bumps ARC prebuild toolchain to arc-2017.09-rc1
> > 
> > There might be subtle differences between uClibc configuration
> > compared to Buildroot's one. Native RPC now is disabled?
> > because uClinc-ng has removed it.
> 
> ?These two sentences are unrelated, right? I mean, Buildroot's uClibc hasn't had
> RPC since April... So better make that two paragraphs.

Probably so.

> ?Could you describe the subtle differences?

Well we may do a full side-by-side comparison of uClibc's defconfigs
but that barely makes a lot of sense. I mean we used to use some configuration
which was formed as it was in years and not all choices I may justify and explain.

Still we're slowly drifting to Buildroot's uClibc defconfig with pretty much every
our release but not yet there... and Buildroot's defconfig changes with time but
we cannot change ours in the middle of development cycle.

Again we may do that comparison and identify all [meaningful] differences
but not sure what it gives.

> > 
> > 
> > Signed-off-by: Evgeniy Didin <didin@synopsys.com>
> > Cc: Alexey Brodkin <abrodkin@synopsys.com>
> > Cc: arc-buildroot at synopsys.com
> > Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> > 
> > ---
> > ?.../toolchain-external/toolchain-external-synopsys-arc/Config.in??| 8 ++++----
> > ?.../toolchain-external-synopsys-arc.hash??????????????????????????| 8 ++++----
> > ?.../toolchain-external-synopsys-arc.mk????????????????????????????| 4 ++--
> > ?3 files changed, 10 insertions(+), 10 deletions(-)
> > 
> > diff --git a/toolchain/toolchain-external/toolchain-external-synopsys-arc/Config.in b/toolchain/toolchain-external/toolchain-external-synopsys-
> > arc/Config.in
> > index f438ea765d..cdf36d08e6 100644
> > --- a/toolchain/toolchain-external/toolchain-external-synopsys-arc/Config.in
> > +++ b/toolchain/toolchain-external/toolchain-external-synopsys-arc/Config.in
> > @@ -1,18 +1,18 @@
> > ?config BR2_TOOLCHAIN_EXTERNAL_SYNOPSYS_ARC
> > -	bool "Synopsys ARC 2016.09 toolchain"
> > +	bool "Synopsys ARC 2017.09-rc1 toolchain"
> 
> ?Do we really want the -rc1 toolchain? Shouldn't we wait for the release? It
> can't be because you want additional testing in the autobuilders, since this
> toolchain doesn't appear in support/config-fragments/autobuild.

Well we used to have ARC prebuilt toolchain in autobuilder if I'm not mistaken.
But due to some significant deviations from Buildroot defaults like missing IPv6
back in the day it got nuked. Maybe Thomas can remember it better... for some
reason I cannot find any signs of ARC prebuilt tools in
https://git.busybox.net/buildroot-test/?so I might be wrong here.

But indeed we wanted to get some more testing for that pre-built toolchain
and catch a couple of issues before cutting rc2 and final release.

And essentially once and if that patch gets accepted the plan was to
submit a config-fragment for it.

> > 
> > ?	depends on BR2_arc
> > ?	depends on BR2_HOSTARCH = "x86_64"
> > ?	select BR2_TOOLCHAIN_EXTERNAL_UCLIBC
> > ?	select BR2_INSTALL_LIBSTDCPP
> > -	select BR2_TOOLCHAIN_HAS_NATIVE_RPC
> > +	#select BR2_TOOLCHAIN_HAS_NATIVE_RPC
> 
> ?You shouldn't comment this line, just remove it.

Good catch - we'll fix that.

-Alexey

  reply	other threads:[~2017-10-11 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-11  9:17 [Buildroot] [PATCH] extern-toolchain: Bump ARC tools to arc-2017.09-rc1 Evgeniy Didin
2017-10-11 20:14 ` Arnout Vandecappelle
2017-10-11 20:51   ` Alexey Brodkin [this message]
2017-10-11 21:13     ` Arnout Vandecappelle

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=1507755106.3839.19.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox