From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Xuanhao Shi via buildroot <buildroot@buildroot.org>
Cc: Xuanhao Shi <x-shi@ti.com>, Suniel Mahesh <sunil@amarulasolutions.com>
Subject: Re: [Buildroot] [PATCH 1/4] package/arm-gnu-toolchain: add version selection
Date: Tue, 26 Jul 2022 19:37:35 +0200 [thread overview]
Message-ID: <20220726193735.735588e4@windsurf> (raw)
In-Reply-To: <20220726165041.17584-2-x-shi@ti.com>
Hello,
On Tue, 26 Jul 2022 11:50:38 -0500
Xuanhao Shi via buildroot <buildroot@buildroot.org> wrote:
> Adds a way to select a custom toolchain link and
> source instead of always using verion 11.2 due
version -> version
> to bugs in the newest version.
Could you give some details on the "bugs" ?
> diff --git a/package/arm-gnu-toolchain/Config.in.host b/package/arm-gnu-toolchain/Config.in.host
> new file mode 100644
> index 0000000000..25d0af1d04
> --- /dev/null
> +++ b/package/arm-gnu-toolchain/Config.in.host
> @@ -0,0 +1,38 @@
> +config BR2_PACKAGE_HOST_ARM_GNU_TOOLCHAIN
> + bool "host arm-gnu-toolchain"
> + help
> + Separate ARM32 cross-compilation toolchain
> + for some AArch64 platforms.
> +
> +menu "host arm-gnu-toolchain version"
> + depends on BR2_PACKAGE_HOST_ARM_GNU_TOOLCHAIN
The menu is not needed.
Use:
if BR2_PACKAGE_HOST_ARM_GNU_TOOLCHAIN
...
endif
to enclose the options of this package.
> +choice
> + bool "host arm-gnu-toolchain version"
Just "version"
> +config BR2_PACKAGE_HOST_ARM_GNU_TOOLCHAIN_DEFAULT
> + bool "Version 11.2-2022.02"
> + help
> + Use version 11.2.
> +
> +config BR2_PACKAGE_HOST_ARM_GNU_TOOLCHAIN_CUSTOM
> + bool "Custom archived sources"
> + help
> + Specify custom archive for the toolchain.
Seeing what you end up needing in your defconfig, I think I would
prefer explicit options for 11.x and 10.x, rather than all this
"custom" mess.
So just:
config BR2_PACKAGE_HOST_ARM_GNU_TOOLCHAIN_VERSION_11_X
...
config BR2_PACKAGE_HOST_ARM_GNU_TOOLCHAIN_VERSION_10_X
...
Thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-26 17:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 16:50 [Buildroot] [PATCH 0/4] add support for TI's AM6X SoCs Xuanhao Shi via buildroot
2022-07-26 16:50 ` [Buildroot] [PATCH 1/4] package/arm-gnu-toolchain: add version selection Xuanhao Shi via buildroot
2022-07-26 17:37 ` Thomas Petazzoni via buildroot [this message]
2022-07-26 19:32 ` Xuanhao Shi via buildroot
2022-07-26 20:07 ` Thomas Petazzoni via buildroot
2022-07-26 21:29 ` Xuanhao Shi via buildroot
2022-07-26 16:50 ` [Buildroot] [PATCH 2/4] package/k3-image-gen: new package Xuanhao Shi via buildroot
2022-07-26 18:55 ` Thomas Petazzoni via buildroot
2022-07-26 20:56 ` Xuanhao Shi via buildroot
2022-07-26 21:07 ` Thomas Petazzoni via buildroot
2022-07-26 21:31 ` Xuanhao Shi via buildroot
2022-07-27 8:22 ` Arnout Vandecappelle
2022-07-26 16:50 ` [Buildroot] [PATCH 3/4] board/am6x: add new board support Xuanhao Shi via buildroot
2022-07-26 18:58 ` Thomas Petazzoni via buildroot
2022-07-26 21:08 ` Xuanhao Shi via buildroot
2022-07-27 8:32 ` Arnout Vandecappelle
2022-07-26 16:50 ` [Buildroot] [PATCH 4/4] configs/am64x_sk_defconfig: add new defconfig Xuanhao Shi via buildroot
2022-07-26 19:00 ` Thomas Petazzoni via buildroot
2022-07-26 21:11 ` Xuanhao Shi via buildroot
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=20220726193735.735588e4@windsurf \
--to=buildroot@buildroot.org \
--cc=sunil@amarulasolutions.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=x-shi@ti.com \
/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.