From: Denys Dmytriyenko <denis@denix.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org,
Denys Dmytriyenko <denys@konsulko.com>
Subject: Re: [OE-core] [RFC PATCH 3/5] musl: set compatibility a bit more flexible
Date: Thu, 2 Oct 2025 10:04:04 -0400 [thread overview]
Message-ID: <20251002140404.GC3125@denix.org> (raw)
In-Reply-To: <CAMKF1spcHAvNJtsStzG0OgigTKkU_QHgApdY1m5Q+Zf4aecTRg@mail.gmail.com>
On Wed, Oct 01, 2025 at 07:12:34PM -0700, Khem Raj wrote:
> On Wed, Oct 1, 2025 at 5:08 PM Denys Dmytriyenko via
> lists.openembedded.org <denis=denix.org@lists.openembedded.org> wrote:
> >
> > From: Denys Dmytriyenko <denys@konsulko.com>
> >
> > Like musl Linux config, baremetal also uses musl as a libc, but
> > it has a different host triplet set. Hence adjust COMPATIBLE_HOST
> > to accomodate this use case by checking that musl is a preferred
> > provider of libc.
>
> This sounds a bit odd. Why do we use musl for baremetal targets ?
Was like that for 10 years since the beginning of baremetal support:
https://git.openembedded.org/openembedded-core/commit/?id=cb010e306a6a856c589db5f41fdcaea4e5035d93
> while musl does have FDPIC support but I don't think thats how we
> use it.
>
> >
> > [YOCTO #15982]
> >
> > Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
> > ---
> > meta/recipes-core/musl/bsd-headers.bb | 2 +-
> > meta/recipes-core/musl/libssp-nonshared.bb | 3 ++-
> > 2 files changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/meta/recipes-core/musl/bsd-headers.bb b/meta/recipes-core/musl/bsd-headers.bb
> > index ad9ba81e4f..c6a3814a49 100644
> > --- a/meta/recipes-core/musl/bsd-headers.bb
> > +++ b/meta/recipes-core/musl/bsd-headers.bb
> > @@ -25,7 +25,7 @@ do_install() {
> > #
> > # We will skip parsing for non-musl systems
> > #
> > +COMPATIBLE_HOST = "${@oe.utils.conditional('PREFERRED_PROVIDER_virtual/libc', 'musl', '.*', 'null', d)}"
> >
> > -COMPATIBLE_HOST = ".*-musl.*"
> > DEV_PKG_DEPENDENCY = ""
> > RRECOMMENDS:${PN}-dbg = "${PN}-dev (= ${EXTENDPKGV})"
> > diff --git a/meta/recipes-core/musl/libssp-nonshared.bb b/meta/recipes-core/musl/libssp-nonshared.bb
> > index 4bcbaef7ea..6f12ff0c9b 100644
> > --- a/meta/recipes-core/musl/libssp-nonshared.bb
> > +++ b/meta/recipes-core/musl/libssp-nonshared.bb
> > @@ -29,7 +29,8 @@ do_install() {
> > #
> > # We will skip parsing for non-musl systems
> > #
> > -COMPATIBLE_HOST = ".*-musl.*"
> > +COMPATIBLE_HOST = "${@oe.utils.conditional('PREFERRED_PROVIDER_virtual/libc', 'musl', '.*', 'null', d)}"
> > +
> > RDEPENDS:${PN}-staticdev = ""
> > DEV_PKG_DEPENDENCY = ""
> > RRECOMMENDS:${PN}-dbg = "${PN}-staticdev (= ${EXTENDPKGV})"
> > --
> > 2.25.1
next prev parent reply other threads:[~2025-10-02 14:04 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 ` [RFC PATCH 2/5] glibc: skip also on baremetal Denys Dmytriyenko
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 [this message]
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=20251002140404.GC3125@denix.org \
--to=denis@denix.org \
--cc=denys@konsulko.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.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