From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH V2 3/9] arch/csky: Add toolchain build framework.
Date: Sun, 26 May 2019 22:44:52 +0200 [thread overview]
Message-ID: <20190526224452.64efb0f7@windsurf> (raw)
In-Reply-To: <1557305915-11247-3-git-send-email-guoren@kernel.org>
On Wed, 8 May 2019 16:58:29 +0800
guoren at kernel.org wrote:
> From: Guo Ren <ren_guo@c-sky.com>
>
> Enable csky buildroot build toolchain in framework.
>
> Signed-off-by: Guo Ren <ren_guo@c-sky.com>
> ---
> arch/Config.in | 1 -
> package/Makefile.in | 9 +++++++++
> 2 files changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/arch/Config.in b/arch/Config.in
> index d82803c..db1199c 100644
> --- a/arch/Config.in
> +++ b/arch/Config.in
> @@ -77,7 +77,6 @@ config BR2_aarch64_be
>
> config BR2_csky
> bool "csky"
> - select BR2_ARCH_HAS_NO_TOOLCHAIN_BUILDROOT
The ordering is not good: you can't remove this "select" until all the
toolchain components have C-SKY support added. So this patch should
come later in the series, it should actually be one of the last patch,
and should be: "arch/csky: enable internal toolchain backend" or
something like that.
> diff --git a/package/Makefile.in b/package/Makefile.in
> index dc818a2..f05b9cc 100644
> --- a/package/Makefile.in
> +++ b/package/Makefile.in
> @@ -70,6 +70,15 @@ ABI := $(ABI)hf
> endif
> endif
>
> +# For C-SKY abiv1 & abiv2
> +ifeq ($(BR2_csky),y)
> +ifeq ($(BR2_ck610),y)
> +ABI = abiv1
> +else
> +ABI = abiv2
> +endif
> +endif
This should be a separate patch.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-26 20:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 8:58 [Buildroot] [PATCH V2 1/9] arch/csky: Add VDSP and FLOAT_ABI compiler options guoren at kernel.org
2019-05-08 8:58 ` [Buildroot] [PATCH V2 2/9] arch/csky: Add ck860 and -mcpu " guoren at kernel.org
2019-05-26 20:43 ` Thomas Petazzoni
2019-05-27 6:43 ` Guo Ren
2019-05-08 8:58 ` [Buildroot] [PATCH V2 3/9] arch/csky: Add toolchain build framework guoren at kernel.org
2019-05-26 20:44 ` Thomas Petazzoni [this message]
2019-05-27 6:52 ` Guo Ren
2019-05-08 8:58 ` [Buildroot] [PATCH V2 4/9] package/binutils: Add C-SKY support guoren at kernel.org
2019-05-26 20:52 ` Thomas Petazzoni
2019-05-27 7:23 ` Guo Ren
2019-05-08 8:58 ` [Buildroot] [PATCH V2 5/9] package/gcc: " guoren at kernel.org
2019-05-26 20:53 ` Thomas Petazzoni
2019-05-27 7:27 ` Guo Ren
2019-05-08 8:58 ` [Buildroot] [PATCH V2 6/9] package/gdb: " guoren at kernel.org
2019-05-26 20:56 ` Thomas Petazzoni
2019-05-27 8:08 ` Guo Ren
2019-05-08 8:58 ` [Buildroot] [PATCH V2 7/9] package/glibc: " guoren at kernel.org
2019-05-26 20:57 ` Thomas Petazzoni
2019-05-27 8:11 ` Guo Ren
2019-05-08 8:58 ` [Buildroot] [PATCH V2 8/9] support/config.sub: " guoren at kernel.org
2019-05-27 20:30 ` Thomas Petazzoni
2019-05-27 22:00 ` Peter Korsgaard
2019-05-28 6:55 ` Thomas Petazzoni
2019-06-06 15:19 ` Peter Korsgaard
2019-05-08 8:58 ` [Buildroot] [PATCH V2 9/9] configs/qemu_cskyXXX_virt: new defconfig guoren at kernel.org
2019-05-13 5:46 ` [Buildroot] [PATCH V2 1/9] arch/csky: Add VDSP and FLOAT_ABI compiler options Guo Ren
2019-05-26 20:39 ` Thomas Petazzoni
2019-05-26 20:40 ` Thomas Petazzoni
2019-05-27 11:35 ` Guo Ren
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=20190526224452.64efb0f7@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox