[meta-virtualization][PATCH 3/4] podman: Use gcc-based toolchain

[meta-virtualization][PATCH 3/4] podman: Use gcc-based toolchain

[Andrei Gherzan]

From: Andrei Gherzan <andrei.gherzan@huawei.com>

clang-based builds are still broken due to:
https://github.com/llvm/llvm-project/issues/53999

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
---
 recipes-containers/podman/podman_git.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/recipes-containers/podman/podman_git.bb b/recipes-containers/podman/podman_git.bb
index 2bbc4dc..9b92094 100644
--- a/recipes-containers/podman/podman_git.bb
+++ b/recipes-containers/podman/podman_git.bb
@@ -44,6 +44,9 @@ exclude_graphdriver_btrfs exclude_graphdriver_devicemapper"
 # overide LDFLAGS to allow podman to build without: "flag provided but not # defined: -Wl,-O1
 export LDFLAGS=""
 
+# https://github.com/llvm/llvm-project/issues/53999
+TOOLCHAIN = "gcc"
+
 inherit go goarch
 inherit systemd pkgconfig
 
-- 
2.25.1

[meta-virtualization][PATCH 4/4] cni: Use gcc-based toolchain

[Andrei Gherzan]

From: Andrei Gherzan <andrei.gherzan@huawei.com>

clang-based builds are still broken due to:
https://github.com/llvm/llvm-project/issues/53999

Signed-off-by: Andrei Gherzan <andrei.gherzan@huawei.com>
---
 recipes-networking/cni/cni_git.bb | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/recipes-networking/cni/cni_git.bb b/recipes-networking/cni/cni_git.bb
index 7749312..81988ce 100644
--- a/recipes-networking/cni/cni_git.bb
+++ b/recipes-networking/cni/cni_git.bb
@@ -28,6 +28,9 @@ PV = "v1.1.0+git${SRCREV_cni}"
 inherit go
 inherit goarch
 
+# https://github.com/llvm/llvm-project/issues/53999
+TOOLCHAIN = "gcc"
+
 do_compile() {
 	mkdir -p ${S}/src/github.com/containernetworking
 	ln -sfr ${S}/src/import ${S}/src/github.com/containernetworking/cni
-- 
2.25.1

Re: [meta-virtualization][PATCH 1/4] runc: Backport patch to fix duplicate switch statements

[Andrei Gherzan]

On Thu, 4 Aug 2022, at 04:17, Bruce Ashfield wrote:
> I have a bump of runc pending in master-next, and from my
> check, it has this change already. kirkstone of course, doesn't
> have that, so I've queued the similar patch there.
>

Right. I did see it in the later vendored version but I didn't have the time to test it out.

> But I've pulled the other three into testing, and will have
> them merged shortly.

Cheers for this.

Andrei