Apply the patch from Xen to fix device tree parsing in newer kernels. Signed-off-by: Christopher Clark <christopher.w.clark@...> --- ...issing-device_type-property-in-pci-p.patch | 91

Patch is not needed for image prelinking since the gcc toolchain in this branch successfully links Xen without it. Remove the patch from the stable branch since the BSD license of the modified header

The default preferred Linux kernel for Xen on the Raspberry Pi 4 in this branch is linux-yocto. The alternative provided option is linux-yocto-dev, but this is unintentionally a branch tracking

Apply the patch from Xen to fix device tree parsing in newer kernels and remove the Xen configuration file since the default works. Signed-off-by: Christopher Clark

Patch is not needed for image prelinking since the gcc toolchain in this branch successfully links Xen without it. Remove the patch from the stable branch since the BSD license of the modified header

The default preferred Linux kernel for Xen on the Raspberry Pi 4 board in this branch is linux-yocto-dev, which unfortunately results in a branch tracking configuration rather than a fixed

Apply the patch from Xen to fix device tree parsing in newer kernels and remove the Xen configuration file since the default works. Signed-off-by: Christopher Clark

Patch is not needed for image prelinking since the gcc toolchain in this branch successfully links Xen without it. Remove the patch from the stable branch since the BSD license of the modified header

The default preferred Linux kernel for Xen on the Raspberry Pi 4 board in this branch is linux-yocto-dev, which unfortunately results in a branch tracking configuration rather than a fixed

A series of fixes applied to master and across stable branches where needed to fix running Xen on the Raspberry Pi 4 board. This updates Linux kernel configuration for Xen to remove tracking from the

Sounds good, thank you for taking a look!

ok, so this is specific to those distros. Since there are quite a few different CI pipelines, and my own local builds that aren't seeing the error. ok, cool. Nothing strange in that

Apologies for being vague. podman fails to compile, on both Ubuntu 18.04 and Fedora 35, using the latest master branch of bitbake, openembedded-core, meta-openembedded and meta-virtualization. Below

We need a better description here. What is the intent of the recipe ? Is it being run on the target (it isn't a -native recipe, so that is the implication). How would someone use it ? How would I

I'm building podman nightly without seeing this error. So your message about "people using only oe-core" doesn't make sense, can you clarify ? Bruce -- - Thou shalt not follow the NULL pointer,

buildah is a tool that facilitates building OCI container images. Signed-off-by: Sakib Sajal <sakib.sajal@...> --- recipes-containers/buildah/buildah_git.bb | 57 +++++++++++++++++++++++ 1

I would love to resolve the issue, but I am trying to make progress as I am going to submit a recipe for buildah which depends on podman. Sakib

When using oe-core, podman do_compile fails with the error: .../podman/4.0.1+gitAUTOINC+717edd7b84-r0/recipe-sysroot-native/usr/bin/go-md2man: No such file or directory make: ***

Hi Bruce, Great, thanks a lot :-) Cheers Bertrand

<christopher.w.clark@...> wrote: Everything is merged to master and kirkstone. Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force