From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Frager, Neal" <neal.frager@amd.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] toolchain-bare-metal-buildroot
Date: Thu, 27 Feb 2025 18:26:29 +0100 [thread overview]
Message-ID: <20250227182629.01faf186@windsurf> (raw)
In-Reply-To: <SA1PR12MB561598FDC7DDED2E1FC57054F0CD2@SA1PR12MB5615.namprd12.prod.outlook.com>
Hello,
On Thu, 27 Feb 2025 12:58:34 +0000
"Frager, Neal" <neal.frager@amd.com> wrote:
> I am continuing the work on the toolchain-bare-metal-buildroot, and I have
> encountered a snag where I am hoping you can come up with a brilliant idea
> to resolve.
>
> In addition to needing multiple bare-metal toolchains, the versal gen2 products
> need the riscv32 toolchain to have "--with-arch=rv32imc" included in the
> configuration. Just using the riscv32 tuple is not sufficient.
>
> Since the architecture tuples come as a list, do you have any ideas for
> how we can handle architectures that have many options beyond just the
> tuple, such as ARM and RISC-V? Any additional variables we make will
> also need to be a list.
>
> Do you have any ideas for a clean way to handle this? Perhaps arch
> specific configs that we can apply in the config loop should the tuple
> match the corresponding option?
I really don't have a good suggestion here unfortunately. This is
another area where a kconfig-based configuration system is showing its
limits IMO.
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:[~2025-02-27 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 12:58 [Buildroot] toolchain-bare-metal-buildroot Frager, Neal via buildroot
2025-02-27 17:26 ` Thomas Petazzoni via buildroot [this message]
2025-03-04 22:28 ` Arnout Vandecappelle via buildroot
2025-03-05 7:19 ` Frager, Neal via buildroot
2025-06-18 21:41 ` Frager, Neal via buildroot
2025-06-18 21:46 ` Frager, Neal 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=20250227182629.01faf186@windsurf \
--to=buildroot@buildroot.org \
--cc=neal.frager@amd.com \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox