From: Thomas Perrot <thomas.perrot@bootlin.com>
To: raj.khem@gmail.com
Cc: thomas.perrot@bootlin.com,
openembedded-core@lists.openembedded.org,
thomas.petazzoni@bootlin.com
Subject: Re: [OE-core][PATCH] opensbi: force gcc toolchain
Date: Tue, 03 Feb 2026 18:02:17 +0100 [thread overview]
Message-ID: <60a0590f584c498d5fff88f016c2bd9d0df864b2.camel@bootlin.com> (raw)
In-Reply-To: <CAMKF1sqD8T-5g8S2nhDEivcg84U0Kw3GjnAs_0qDqKqy13_Q1A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2323 bytes --]
Hello Khem,
On Thu, 2026-01-22 at 09:19 -0800, Khem Raj via lists.openembedded.org
wrote:
>
>
> On Thu, Jan 22, 2026 at 7:31 AM Thomas Perrot via
> lists.openembedded.org
> <thomas.perrot=bootlin.com@lists.openembedded.org> wrote:
> > From: Thomas Perrot <thomas.perrot@bootlin.com>
> >
> > OpenSBI requires the gcc toolchain to build correctly. Set
> > TOOLCHAIN
> > explicitly to prevent build failures when using alternative
> > toolchains.
> >
>
>
> I am assuming you are having issues compiling it with clang, it would
> be good to document whats going wrong.
> Since it's a bug to address, openSBI does not intend to use a
> particular compiler.
>
We are figuring out the linker issue when Clang is used as the default
toolchain. We haven't taken the time to figure it out yet.
Kind regards,
Thomas Perrot
> >
> > Signed-off-by: Thomas Perrot <thomas.perrot@bootlin.com>
> > ---
> > meta/recipes-bsp/opensbi/opensbi_1.8.1.bb | 2 ++
> > 1 file changed, 2 insertions(+)
> >
> > diff --git a/meta/recipes-bsp/opensbi/opensbi_1.8.1.bb
> > b/meta/recipes-bsp/opensbi/opensbi_1.8.1.bb
> > index 0a9652c2831e..52d7b38ff2ba 100644
> > --- a/meta/recipes-bsp/opensbi/opensbi_1.8.1.bb
> > +++ b/meta/recipes-bsp/opensbi/opensbi_1.8.1.bb
> > @@ -15,6 +15,8 @@ TARGET_DBGSRC_DIR =
> > "/share/opensbi/*/generic/firmware/"
> >
> > TARGET_CC_ARCH += "${LDFLAGS}"
> >
> > +TOOLCHAIN = "gcc"
> > +
> > RISCV_SBI_FW_TEXT_START ??= "0x80000000"
> > EXTRA_OEMAKE += "REPRODUCIBLE=y CROSS_COMPILE=${HOST_PREFIX}
> > ELFFLAGS="${LDFLAGS}" PLATFORM=${RISCV_SBI_PLAT} I=${D}
> > FW_TEXT_START=${RISCV_SBI_FW_TEXT_START}"
> > EXTRA_OEMAKE:append:toolchain-clang = " LLVM=y"
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#229853):
> > https://lists.openembedded.org/g/openembedded-core/message/229853
> > Mute This Topic:
> > https://lists.openembedded.org/mt/117401535/5443093
> > Group Owner: openembedded-core+owner@lists.openembedded.org
> > Unsubscribe:
> > https://lists.openembedded.org/g/openembedded-core/unsub [
> > thomas.perrot@bootlin.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
--
Thomas Perrot, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
[-- Attachment #1.2: Type: text/html, Size: 4455 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2026-02-03 17:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 15:30 [OE-core][PATCH] opensbi: force gcc toolchain thomas.perrot
2026-01-22 17:19 ` Khem Raj
2026-02-03 17:02 ` Thomas Perrot [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=60a0590f584c498d5fff88f016c2bd9d0df864b2.camel@bootlin.com \
--to=thomas.perrot@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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