From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Neal Frager <neal.frager@amd.com>
Cc: buildroot@buildroot.org, ibai.erkiaga-elorza@amd.com,
luca.ceresoli@bootlin.com, brandon.maier@collins.com,
thomas.petazzoni@bootlin.com, romain.naour@smile.fr,
michal.simek@amd.com, romain.naour@gmail.com
Subject: Re: [Buildroot] [PATCH v1 1/1] toolchain/toolchain-bare-metal-buildroot: add multilib option
Date: Wed, 24 Sep 2025 22:20:29 +0200 [thread overview]
Message-ID: <7f9348dcffb7e934e439f458ce656306@free.fr> (raw)
In-Reply-To: <20250619154811.936265-1-neal.frager@amd.com>
On 19/06/2025 17:48, Neal Frager via buildroot wrote:
> Sometimes the default GCC and newlib libraries built for a given
> architecture tuple are not based on the desired ABI. Since ABI
> definitions are
> different between architectures, the simplest solution is to allow
> users to
> build bare-metal toolchains with --enable-multilib. This way, the
> libraries
> for every available ABI will be built and users will be able to select
> the
> desired library for their user applications.
>
> This patch adds the option BR2_TOOLCHAIN_BARE_METAL_BUILDROOT_MULTILIB
> to give
> users the choice to enable multilib, if desired.
>
> Please note that when using a string of architecture tuples, this
> option will
> apply to all architectures in the string, so it can significantly
> increase
> build time.
>
> Signed-off-by: Neal Frager <neal.frager@amd.com>
Applied to master, thanks.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-09-24 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 15:48 [Buildroot] [PATCH v1 1/1] toolchain/toolchain-bare-metal-buildroot: add multilib option Neal Frager via buildroot
2025-08-18 15:03 ` [Buildroot] [PATCH v1 1/1], " Jesse Taube
2025-09-01 8:46 ` [Buildroot] [PATCH v1 1/1] " Frager, Neal via buildroot
2025-09-24 20:20 ` Julien Olivain via buildroot [this message]
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=7f9348dcffb7e934e439f458ce656306@free.fr \
--to=buildroot@buildroot.org \
--cc=brandon.maier@collins.com \
--cc=ibai.erkiaga-elorza@amd.com \
--cc=ju.o@free.fr \
--cc=luca.ceresoli@bootlin.com \
--cc=michal.simek@amd.com \
--cc=neal.frager@amd.com \
--cc=romain.naour@gmail.com \
--cc=romain.naour@smile.fr \
--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 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.