go.bbclass already inherits goarch.bbclass. The CGO_CFLAGS and CGO_LDFLAGS should use target flags as set in oe-core's go.bbclass, not the SDK related ones. Signed-off-by: Chen Qi

go.bbclass already inherits goarch.bbclass. The CGO_CFLAGS and CGO_LDFLAGS should use target flags as set in oe-core's go.bbclass, not the SDK related ones. Signed-off-by: Chen Qi

go.bbclass already inherits goarch.bbclass. The CGO_CFLAGS and CGO_LDFLAGS should use target flags as set in oe-core's go.bbclass, not the SDK related ones. Signed-off-by: Chen Qi

go.bbclass already inherits goarch.bbclass. The CGO_CFLAGS and CGO_LDFLAGS should use target flags as set in oe-core's go.bbclass, not the SDK related ones. Signed-off-by: Chen Qi

According to https://github.com/containers/skopeo/blob/main/install.md#building-from-source, the ostree dependency is not needed. Also, remove the CGO settings which incorrectly use BUILDSDK_XXX. The

v2.8.1 is the latest stable version. Signed-off-by: Chen Qi <Qi.Chen@...> --- .../docker-distribution/docker-distribution_git.bb | 6 +++--- 1 file changed, 3 insertions(+), 3

The CGO_CFLAGS and other related variables have already been set appropriately by the go.bbclass in oe-core. Setting them in this recipe is not only unncessary but also error prone. For example

In order for systemd variables such as SYSTEMD_AUTO_ENABLE to have effect, we need to inherit the systemd class. We also need to specify the package which contains the service. As go.bbclass already

Hi Michal, Reviewed-by: Bertrand Marquis <bertrand.marquis@...> Also tested on kirkstone and dom0 boots fine and pci is working. Thanks a lot Cheers Bertrand

Hi Michal, Reviewed-by: Bertrand Marquis <bertrand.marquis@...> Also tested on kirkstone and dom0 boots fine and pci is working. Thanks a lot Cheers Bertrand

By default, highmem option is enabled for machine types later than virt-2.12. This allows qemu to place devices and RAM in physical address space above 32-bits. This can cause issues as according to

This reverts commit fb0a7b97db4f419b82309f98a4944ae3330d1e2e. Justification: Commit fb0a7b97db4f removed the PCI node from the qemu device tree due to the issue when trying to access PCI

This series acts as a follow-up to the commit: fb0a7b97db4f ("xen: Disable PCI on qemuarm with Xen") This wants to be backported to kirkstone. Michal Orzel (2): Revert "xen: Disable PCI on qemuarm

Hi Bruce, From: Bruce Ashfield <bruce.ashfield@...> Sent: 08 June 2022 17:47 To: Diego Sueiro <Diego.Sueiro@...> Cc: meta-virtualization@... <meta-virtualization@...>; nd <nd@...> Subject: Re:

I've been working on updating k3s to the same format as nerdctl (with .inc files and better formatted dependencies), so let me finish that update, and then we can get this applied. I'll also need to

All repositories under https://go.googlesource.com/ have a mirror in https://github.com. Fetching the dependencies from github is much faster and we avoid timeouts = due to googlesource

In order for systemd variables such as SYSTEMD_AUTO_ENABLE to have effect, we need to inherit the systemd class. We also need to specify the package which contains the service. As go.bbclass already

Fix typo: RDPENDS_${PN} -> RDEPENDS:${PN} Signed-off-by: Yi Zhao <yi.zhao@...> --- .../recipes-devtools/python/python3-heat-cfntools_1.4.2.bb | 2 +- 1 file changed, 1 insertion(+), 1

I do see the ":)" at the end of that statement .. but since we have no idea who "yocto@" is .. don't expect a full/proper answer. If you would have checked master-next, you can see the in

Wow great can we get crio and podman updated now also :)