I wonder about this patch series. Shouldn't we rather check if incompatible items can be made compatible, instead of simply giving up without even trying, and then propagating architecture disabling throughout recipes?
For example, grub does support loongarch64: https://git.savannah.gnu.org/cgit/grub.git/tree/grub-core/kern/loongarch64 I'd also like to see what happens when valgrind is actually built for that architecture, and have it documented in commit messages. And kexec-tools as well. Alex On Sat, 28 Dec 2024 at 10:06, hongxu via lists.openembedded.org <hongxu.jia=eng.windriver....@lists.openembedded.org> wrote: > > Due to initramfs-module-install runtime depend on grub, and grub did not > support loongarch64, remove loongarch64 from COMPATIBLE_HOST > > $ echo "MACHINE = 'qemuloongarch64'" >> conf/local.conf > $ bitbake world > ERROR: Nothing RPROVIDES 'grub' (but > oe-core/meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb > RDEPENDS on or otherwise requires it) > grub was skipped: incompatible with host loongarch64-wrs-linux (not in > COMPATIBLE_HOST) > NOTE: Runtime target 'grub' is unbuildable, removing... > Missing or unbuildable dependency chain was: ['grub'] > ERROR: Required build target 'meta-world-pkgdata' has no buildable providers. > Missing or unbuildable dependency chain was: ['meta-world-pkgdata', > 'initramfs-module-install', 'grub'] > > Signed-off-by: Hongxu Jia <hongxu....@windriver.com> > --- > meta/recipes-core/images/core-image-minimal-initramfs.bb | 2 +- > meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb | 2 +- > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff --git a/meta/recipes-core/images/core-image-minimal-initramfs.bb > b/meta/recipes-core/images/core-image-minimal-initramfs.bb > index 36e8771c4a..4e210d1bf3 100644 > --- a/meta/recipes-core/images/core-image-minimal-initramfs.bb > +++ b/meta/recipes-core/images/core-image-minimal-initramfs.bb > @@ -32,4 +32,4 @@ IMAGE_ROOTFS_SIZE = "8192" > IMAGE_ROOTFS_EXTRA_SPACE = "0" > > # Use the same restriction as initramfs-module-install > -COMPATIBLE_HOST = > '(x86_64.*|i.86.*|arm.*|aarch64.*|loongarch64.*)-(linux.*|freebsd.*)' > +COMPATIBLE_HOST = '(x86_64.*|i.86.*|arm.*|aarch64.*)-(linux.*|freebsd.*)' > diff --git a/meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb > b/meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb > index b87e59f347..d6d8348731 100644 > --- a/meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb > +++ b/meta/recipes-core/initrdscripts/initramfs-module-install_1.0.bb > @@ -5,7 +5,7 @@ RDEPENDS:${PN} = "initramfs-framework-base grub parted > e2fsprogs-mke2fs util-lin > RRECOMMENDS:${PN} = "${VIRTUAL-RUNTIME_base-utils-syslog}" > > # The same restriction as grub > -COMPATIBLE_HOST = > '(x86_64.*|i.86.*|arm.*|aarch64.*|loongarch64.*)-(linux.*|freebsd.*)' > +COMPATIBLE_HOST = '(x86_64.*|i.86.*|arm.*|aarch64.*)-(linux.*|freebsd.*)' > COMPATIBLE_HOST:armv7a = 'null' > COMPATIBLE_HOST:armv7ve = 'null' > > -- > 2.34.1 > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#209156): https://lists.openembedded.org/g/openembedded-core/message/209156 Mute This Topic: https://lists.openembedded.org/mt/110315561/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
