On 10/7/2026 9:30 AM, Paul Barker wrote:
On Tue, 2026-10-06 at 17:42 -0400, Denys Dmytriyenko wrote:
From: Denys Dmytriyenko <[email protected]>

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 <[email protected]>
---
  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,

That would fix the bad behavior but would result in the same build issue that we see when just removing it. I think the issue might be fixed by the gcc fix that Jeorg sent to the list. I'm going to test this build with his patch right now and see if it fixes everything.






--
Ryan Eatmon                [email protected]
-----------------------------------------
Texas Instruments, Inc.  -  LCPD  -  MGTS
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#247402): 
https://lists.openembedded.org/g/openembedded-core/message/247402
Mute This Topic: https://lists.openembedded.org/mt/121618723/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to