12704 2018-04-20 14:50:16 +0000 Go fails to build on older hosts 2018-04-26 07:59:40 +0000 1 1 7 Build System, Metadata & Runtime OE-Core devtools / tool chain 2.5 x86 Multiple RESOLVED FIXED Medium+ normal 2.5 M4 1 ross.burton matt matt meta.mr.watcher meta.watcher otavio richard.purdie --- --- No (bug/feature does not impact docs) oldest_to_newest 80364 0 ross.burton 2018-04-20 14:50:16 +0000 ERROR: go-runtime-1.9.4-r0 do_compile: Function failed: do_compile (log file is located at /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-world-lsb/build/build/tmp/work/i586-poky-linux/go-runtime/1.9.4-r0/temp/log.do_compile.54340) ... | ##### Building Go toolchain using /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-world-lsb/build/build/tmp/work/i586-poky-linux/go-runtime/1.9.4-r0/recipe-sysroot-native/usr/lib/go. | # runtime/cgo | gcc: error: unrecognized command line option ‘-fstack-protector-strong’ Looks like it's trying to use the host compiler with target CFLAGS, which isn't right. This broke a test-M4 build so hopefully we can get this fixed asap. https://autobuilder.yocto.io/builders/nightly-world-lsb/builds/941/steps/BuildImages/logs/stdio 80367 1 matt 2018-04-21 06:16:19 +0000 The issue is specifically with CGO_CFLAGS and CGO_LDFLAGS, which are being set in go-runtime.inc to the target values. For the go 1.10 runtime build, that's the right setting, since it only builds target binaries. That's not good for the go 1.9 runtime build, though, since it builds the host binaries before building the target binaries. Overriding those settings on the host-side invocation of make.bash should take care of this. 80416 2 richard.purdie 2018-04-26 07:59:40 +0000 http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=00fe24fe8cbec81362e04c4c56ff4d33384cf72c