Created attachment 123479 [details] Dont prefer old rpm Current yocto distro.conf seems to prefer RPM 4.11 over the more recent packages, this seems to be an artifact inherited from gnome-continuous. However, older rpm does not recognize the arm-unknown-linux-gnueabi triples for the armv7a builds. Removing this preference allows the yocto build scripts to successfully create and extract packages with rpm when building for armv7a on an aarch64 host.
rpm 5 is not just "the latest". Its a crazy fork that most of the rpm-using distros are not using.
(In reply to Alexander Larsson from comment #1) > rpm 5 is not just "the latest". Its a crazy fork that most of the rpm-using > distros are not using. rpm 4 is not well supported in poky and obviously has some issues, note that support for rpm 4 is removed completely in this commit: https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/meta/recipes-devtools/rpm?id=1e9de52ca0d3765ca47ec18fc9e71172257ff3c1 Citing: "RPM4 support is buggy and incomplete. As we don't have the resources or interest to maintain it this patch removes it." FWIW to be more specific about the exact problem: rpm 4.11 as built in yocto has a bug when creating the packages for the target, it ends up encoding 'gnueabi' as the %{OS} tag in the package metadata instead of 'linux' (it presumably interprets the arm-unknown-linux-gnueabi triple incorrectly), this breaks when trying to extract the packages later in the target sysroot, with a problem like: "package was intended for another operating system". Seeing as generating rpms is not really even a feature/output of this build but rather just an implementation detail of creating a rootfs with the bitbake scripts; I think that: a.) its not worth the energy to try to fix the rpm 4.11 build in yocto while the default 5.x build works fine for our purposes b.) we're actually better off just using whatever is well supported by upstream yocto anyway (4.11 will be gone in the next poky release branch anyway) Thoughts ?
Created attachment 123526 [details] [review] This patch removes the 4.11 configurations completely This is another version of the same patch which I forgot to update here the other day after testing that the whole build works after removing these few lines entirely instead of just changing the preferred version.
Makes sense, pushed.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.