From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: Evgeniy Didin <Evgeniy.Didin@synopsys.com>,
arcml <linux-snps-arc@lists.infradead.org>,
Alexey Brodkin <Alexey.Brodkin@synopsys.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [PATCH v2] binutils/ARC: cleanup
Date: Fri, 11 Sep 2020 11:18:28 +0200 [thread overview]
Message-ID: <20200911111828.5c9ea5d5@windsurf.hq.k.grp> (raw)
In-Reply-To: <3b18564e-be2e-91b3-def1-6c3591288ecc@synopsys.com>
Hello Vineet,
On Thu, 10 Sep 2020 23:21:43 +0000
Vineet Gupta <Vineet.Gupta1@synopsys.com> wrote:
> >> -ifeq ($(BINUTILS_VERSION),arc-2019.09-rc1)
> >> +ifeq ($(BR2_BINUTILS_VERSION_ARC),y)
>
> Looks like we need this specific thunk anyways. When I select pristine upstream
> binutils (not ARC fork @ github), the above forces it to download from github
> which it should not and will not if the tag/branch has not been mirrored there.
So I guess you're talking about the situation where a host-binutils is
not enabled, and only a target binutils is used. In this case, indeed:
ifeq ($(BINUTILS_VERSION),)
ifeq ($(BR2_arc),y)
BINUTILS_VERSION = arc-2020.03-release
else
BINUTILS_VERSION = 2.33.1
endif
endif # BINUTILS_VERSION
will kick in and set BINUTILS_VERSION to arc-2020.03-release, which
will lead to:
ifeq ($(BINUTILS_VERSION),arc-2020.03-release)
BINUTILS_SITE = $(call github,foss-for-synopsys-dwc-arc-processors,binutils-gdb,$(BINUTILS_VERSION))
BINUTILS_SOURCE = binutils-gdb-$(BINUTILS_VERSION).tar.gz
BINUTILS_FROM_GIT = y
endif
being taken into account.
What happens with target binutils is:
(1) If a host-binutils is built (because Buildroot is building the
toolchain), then we're using the same version as the
host-binutils, which is defined by the choice in
package/binutils/Config.in.host.
(2) If not host-binutils is built (because we're using an external
toolchain), then there is no version selection: we unconditionally
use 2.33.1, except on ARC where we use the special ARC fork.
So I guess the decision to take is: do we want to switch to using the
upstream binutils, even for ARC, when no host-binutils is built ?
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
next prev parent reply other threads:[~2020-09-11 9:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-06 19:39 [PATCH 0/3] ARC toolchian related fixes Vineet Gupta
2019-12-06 19:39 ` [PATCH 1/3] toolchain,glibc: Allow ARC big endian glibc builds Vineet Gupta
2019-12-06 21:18 ` [Buildroot] [PATCH 1/3] toolchain, glibc: " Thomas Petazzoni
2019-12-06 19:39 ` [PATCH 2/3] binutils/ARC: move ARC specific code together Vineet Gupta
2019-12-06 21:19 ` [Buildroot] " Thomas Petazzoni
2019-12-17 21:32 ` [PATCH v2] binutils/ARC: cleanup Vineet Gupta
2019-12-22 21:41 ` [Buildroot] " Thomas Petazzoni
2020-01-13 17:48 ` Vineet Gupta
2020-09-10 23:21 ` Vineet Gupta
2020-09-11 9:18 ` Thomas Petazzoni [this message]
2020-09-11 19:37 ` Vineet Gupta
2019-12-06 19:39 ` [PATCH 3/3] toolchain/ARC: Enable ability to build with upstream gcc/binutils Vineet Gupta
2019-12-06 21:26 ` [Buildroot] " Thomas Petazzoni
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=20200911111828.5c9ea5d5@windsurf.hq.k.grp \
--to=thomas.petazzoni@bootlin.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Evgeniy.Didin@synopsys.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=buildroot@buildroot.org \
--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