From: Paul Barker <paul@pbarker.dev>
To: Denys Dmytriyenko <denis@denix.org>,
openembedded-core@lists.openembedded.org
Cc: Denys Dmytriyenko <denys@konsulko.com>
Subject: Re: [PATCH] Revert "tclibc-baremetal.inc: fix gcc-cross EXTRA_OECONF"
Date: Wed, 07 Oct 2026 15:30:10 +0100 [thread overview]
Message-ID: <9032ce70465fe1664635c7a3c4eef470c774092e.camel@pbarker.dev> (raw)
In-Reply-To: <20261006214254.1556824-1-denis@denix.org>
On Tue, 2026-10-06 at 17:42 -0400, Denys Dmytriyenko wrote:
> From: Denys Dmytriyenko <denys@konsulko.com>
>
> While this change has good intentions, unfortunaly, it completely
> breaks baremetal setup (at least for ARM arch).
>
> The line this change removes seems to mask an underlying issue,
> but until that issue is fully understood and resolved, let's
> revert it and restore the working baremetal behavior.
>
> For more details please see the following discussion:
> https://lists.openembedded.org/g/openembedded-core/topic/121486589
>
> This reverts commit 020d5f018616bc48eae3a23d5498dec3c78a1386.
>
> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
> ---
> meta/conf/distro/include/tclibc-baremetal.inc | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/meta/conf/distro/include/tclibc-baremetal.inc b/meta/conf/distro/include/tclibc-baremetal.inc
> index 6043cb6654..abea5a7162 100644
> --- a/meta/conf/distro/include/tclibc-baremetal.inc
> +++ b/meta/conf/distro/include/tclibc-baremetal.inc
> @@ -18,6 +18,7 @@ USE_NLS ?= "no"
> IMAGE_LINGUAS = ""
> LIBC_DEPENDENCIES = ""
>
> +EXTRA_OECONF:pn-gcc-cross-${TARGET_ARCH}:append = " --without-headers"
Hi Denys,
I wonder if the fix is that this should be:
EXTRA_OECONF:append:pn-gcc-cross-${TARGET_ARCH}
Best regards,
--
Paul Barker
next prev parent reply other threads:[~2026-10-07 14:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 21:42 [PATCH] Revert "tclibc-baremetal.inc: fix gcc-cross EXTRA_OECONF" Denys Dmytriyenko
2026-10-07 6:01 ` [OE-core] " Jörg Vehlow
2026-10-07 14:30 ` Paul Barker [this message]
2026-10-07 20:13 ` Ryan Eatmon
2026-10-07 20:14 ` Denys Dmytriyenko
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=9032ce70465fe1664635c7a3c4eef470c774092e.camel@pbarker.dev \
--to=paul@pbarker.dev \
--cc=denis@denix.org \
--cc=denys@konsulko.com \
--cc=openembedded-core@lists.openembedded.org \
/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