From: "Oleksandr Hnatiuk" <ohnatiuk@cisco.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] package: disable renamed dependency error if allarch is overridden
Date: Mon, 19 May 2025 03:13:00 -0700 [thread overview]
Message-ID: <23322.1747649580665167105@lists.openembedded.org> (raw)
In-Reply-To: <CANNYZj_MGGaG_GnZB=OtEHqd9xzmq7+2JQePc1szNJxxFNU2hw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 614 bytes --]
How would building packages for SDK work without inheriting nativesdk?
All other packagegroups in this variable use $MACHINE to parametrize themselves, so they are not plain packagegroups either.
Furthermore, they inherit cross-canadian which sets PACKAGE_ARCH in the same way nativesdk.bbclass does.
I cannot know every single detail and history behind why oe-core works the way that it does.
What I do know is that I cannot add certain packages to SDK packagegroup because an unrelated error check is producing a false positive because the possibility of an allarch override is not being accounted for.
[-- Attachment #2: Type: text/html, Size: 703 bytes --]
next prev parent reply other threads:[~2025-05-19 10:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 21:19 [PATCH] package: disable renamed dependency error if allarch is overridden Oleksandr Hnatiuk
2025-05-12 9:02 ` [OE-core] " Alexander Kanavin
2025-05-12 9:31 ` Oleksandr Hnatiuk
2025-05-12 9:40 ` [OE-core] " Alexander Kanavin
2025-05-13 10:30 ` Oleksandr Hnatiuk
2025-05-14 13:16 ` [OE-core] " Alexander Kanavin
2025-05-14 15:35 ` Oleksandr Hnatiuk
2025-05-15 12:55 ` [OE-core] " Alexander Kanavin
2025-05-19 10:13 ` Oleksandr Hnatiuk [this message]
2025-05-19 10:24 ` Oleksandr Hnatiuk
2025-05-20 13:06 ` [OE-core] " Alexander Kanavin
2025-05-20 13:23 ` Richard Purdie
2025-07-10 15:02 ` Oleksandr Hnatiuk
2025-07-11 17:42 ` [OE-core] " Alexander Kanavin
2025-07-25 19:24 ` Oleksandr Hnatiuk
2025-07-26 22:00 ` [OE-core] " Alexander Kanavin
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=23322.1747649580665167105@lists.openembedded.org \
--to=ohnatiuk@cisco.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.