Fix settings for GOROOT, CGO_CFLAGS and CGO_LDFLAGS. The previous setting for GOROOT is no longer valid as the directory does not exist for now. So adjust the GOROOT setting. Currently CGO_CFLAGS is s

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 CGO_CF

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

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 <Qi.Chen@...> --- ..

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 <Qi.Chen@...> --- re

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 <Qi.Chen@...> --- re

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 <Qi.Chen@...> --- re

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 <Qi.Chen@...> --- re

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 deletions(-) diff --git a

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 i

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 i

- reinstall service files - deleted older version Signed-off-by: Lei Maohui <leimaohui@...> --- .../open-iscsi/open-iscsi-user_2.1.4.bb | 60 ---------------------- .../open-iscsi/open-iscsi-user_2.1.7

From: Changqing Li <changqing.li@...> Signed-off-by: Changqing Li <changqing.li@...> --- recipes-containers/criu/criu_git.bb | 6 +-- ...001-criu-Skip-documentation-install.patch} | 14 +++--- ...-Chang

From: Changqing Li <changqing.li@...> Signed-off-by: Changqing Li <changqing.li@...> --- recipes-containers/criu/criu_git.bb | 6 +-- ...001-criu-Skip-documentation-install.patch} | 14 +++--- ...-Chang

There's a QA issue about criu complaining the shebang of crit script is too long. We should replace it with '#!/usr/bin/env python3'. Signed-off-by: Chen Qi <Qi.Chen@...> --- recipes-containers/criu/c

On branch kirkstone, the kata-* recipes clone their sources from github. The git fetcher uses unsafe git protocol by default which Github does not support. This makes the fetch step to fail. One can f

Hi all, On kirkstone branch, the recipe podman-compose_1.0.3.bb specifies the following variables : SRC_URI = "git://github.com/containers/podman-compose.git;branch=devel;protocol=https" SRCREV = "155

From: Changqing Li <changqing.li@...> Signed-off-by: Changqing Li <changqing.li@...> --- recipes-containers/criu/criu_git.bb | 6 +-- ...001-criu-Skip-documentation-install.patch} | 14 +++--- ...-Chang

so ive built yocto with kubernetes k8s flavor, image created and booted, ive done this before with overc which back then worked fine, yet vanilla yocto master seems to have issue swapoff -a k8sinit ro

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