Hi Ross, I've just tracked down to this patch about k8s build failure for arm. I'm now setting the preferred provider to 'go-native' to avoid k8s build regression. go-native contains patches like 0001-allow-CC-and-CXX-to-have-multiple-words.patch. These patches seem to make sense. Do you have any idea how to deal with such situation? Best Regards, Chen Qi On 06/17/2020 01:05 AM, Ross Burton wrote: > From: Ross Burton > > go-binary-native is faster and more portable than go-native, so use it > by default. > > Signed-off-by: Ross Burton > --- > meta/conf/distro/include/tcmode-default.inc | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/meta/conf/distro/include/tcmode-default.inc b/meta/conf/distro/include/tcmode-default.inc > index ab4333144b..7103e10d3b 100644 > --- a/meta/conf/distro/include/tcmode-default.inc > +++ b/meta/conf/distro/include/tcmode-default.inc > @@ -66,6 +66,10 @@ PREFERRED_VERSION_qemu ?= "${QEMUVERSION}" > PREFERRED_VERSION_qemu-native ?= "${QEMUVERSION}" > PREFERRED_VERSION_nativesdk-qemu ?= "${QEMUVERSION}" > > +# Bootstrap Go using a binary release from golang.org. If you want to bootstrap > +# from source using the C-implemented Go 1.4 (only supports x86-64 hosts) then use > +# go-native. > +PREFERRED_PROVIDER_go-native ?= "go-binary-native" > PREFERRED_VERSION_virtual/${TARGET_PREFIX}go ?= "${GOVERSION}" > PREFERRED_VERSION_go-cross-${TUNE_PKGARCH} ?= "${GOVERSION}" > PREFERRED_VERSION_go-crosssdk-${SDK_ARCH} ?= "${GOVERSION}" > > >