From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-core@lists.openembedded.org
Cc: Denys Dmytriyenko <denys@konsulko.com>
Subject: [RFC PATCH 2/5] glibc: skip also on baremetal
Date: Wed, 1 Oct 2025 20:08:07 -0400 [thread overview]
Message-ID: <20251002000810.226673-2-denis@denix.org> (raw)
In-Reply-To: <20251002000810.226673-1-denis@denix.org>
From: Denys Dmytriyenko <denys@konsulko.com>
Similar to how glibc gets skipped when building musl config, also
skip it when building baremetal config.
[YOCTO #15982]
Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
---
meta/recipes-core/glibc/glibc-common.inc | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-core/glibc/glibc-common.inc b/meta/recipes-core/glibc/glibc-common.inc
index 7422ede04d..30179870a9 100644
--- a/meta/recipes-core/glibc/glibc-common.inc
+++ b/meta/recipes-core/glibc/glibc-common.inc
@@ -21,6 +21,7 @@ ARM_INSTRUCTION_SET:armv6 = "arm"
# this helps in easing out parsing for non-glibc system libraries
#
COMPATIBLE_HOST:libc-musl:class-target = "null"
+COMPATIBLE_HOST:libc-baremetal:class-target = "null"
PV = "2.42+git"
--
2.25.1
next prev parent reply other threads:[~2025-10-02 0:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 0:08 [RFC PATCH 1/5] baremetal, linux-dummy: bypass kernel dependencies for baremetal Denys Dmytriyenko
2025-10-02 0:08 ` Denys Dmytriyenko [this message]
2025-10-02 0:08 ` [RFC PATCH 3/5] musl: set compatibility a bit more flexible Denys Dmytriyenko
2025-10-02 2:12 ` [OE-core] " Khem Raj
2025-10-02 14:04 ` Denys Dmytriyenko
2025-10-02 17:23 ` Khem Raj
2025-10-02 19:31 ` Denys Dmytriyenko
2025-10-02 0:08 ` [RFC PATCH 4/5] newlib: mark as incompatible with baremetal, which uses musl Denys Dmytriyenko
2025-10-02 0:08 ` [RFC PATCH 5/5] packagegroups, dpkg: extend musl conditionals to baremetal 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=20251002000810.226673-2-denis@denix.org \
--to=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