linux/poky.git/meta/classes/goarch.bbclass, branch master-next2

goarch.bbclass: Simplify logic

2019-04-12T08:29:06+00:00

Further simplification of the go_map_arm() function. (From OE-Core rev: 9c333505897b2bf0d80737c855af31785d23435a) Signed-off-by: Mark Asselstine Signed-off-by: Richard Purdie

goarch.bbclass: use MACHINEOVERRIDES and simplify go_map_arm()

2019-04-10T12:46:17+00:00

Per https://github.com/golang/go/wiki/GoArm we need to set GOARM when cross building for ARMv5, ARMv6 and ARMv7. The current approach of using TUNE_FEATURES can be error prone, as we can see today when attempting to build for Cortex-A7 which results in GOARM=''. Since the value of MACHINEOVERRIDES already consolidates the values of TUNE_FEATURES into something more consistent we can use the overrides mechanism to set GOARM, leaving just a little bit of logic in go_map_arm() to trigger off the arch (basically target vs host) for the setting of GOARM. (From OE-Core rev: 5f48939e26402b77fc3343f326765137f9570f40) Signed-off-by: Mark Asselstine Signed-off-by: Richard Purdie

goarch: Add riscv64

2019-03-21T16:19:23+00:00

Although RISC-V 64-bit doesn't have official golang support there are forks that now exist with at least some support and work is ongoing in the upstream tree. In order to be able to use the goarch class add support for RISC-V. For more details see here: https://github.com/golang/go/issues/27532 (From OE-Core rev: 91e3b2a762124bf5cf923654ef3a7c871b84c82f) Signed-off-by: Alistair Francis Signed-off-by: Richard Purdie

goarch.bbclass: Set CCACHE_DISABLE

2019-01-14T11:35:55+00:00

Go can't be built with ccache. (From OE-Core rev: cf64c9413a2264aa67e26c6302342ff4aa99a575) Signed-off-by: Robert Yang Signed-off-by: Richard Purdie

recipes: Enforce ARM ISA just for arm arches <= armv5

2018-07-18T09:18:42+00:00

armv7+ used thumb2 ISA and it compiles fine with thumb2 issues are only when using thumb1 ISA (From OE-Core rev: c0ef8a91f671f30acd92e2734144f7ddf1acda53) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

goarch.bbclass: set SECURITY_CFLAGS for mips64

2018-06-15T16:56:24+00:00

When include conf/distro/include/security_flags.inc, NOPIE flags are still required for mips64 target builds. Otherwise it fails to build packages such as glide which inherit go.bbclass: | .../tmp-glibc/work/mips64-wrs-linux/glide/0.13.1-r0/recipe-sysroot-native/usr/bin/mips64-wrs-linux/../../libexec/mips64-wrs-linux/ | gcc/mips64-wrs-linux/7.3.0/ld: .../tmp-glibc/work/mips64-wrs-linux/glide/0.13.1-r0/go-tmp/go-link-518447869/go.o: | relocation r_mips_26 against `a local symbol' can not be used when making a shared object; recompile with -fPIC` Use override 'mipsarch' to set SECURITY_CFLAGS for both mips and mips64. (From OE-Core rev: 98b24e9268dc444356ce8bd9ddfec6adcce5e02a) Signed-off-by: Kai Kang Signed-off-by: Richard Purdie

go.bbclass, goarch.bbclass: update SECURITY_CFLAGS

2018-03-06T14:43:10+00:00

With go1.10 the NOPIE flags are only required for MIPS target builds, and are now incompatible for the other architectures. (From OE-Core rev: f2ff90eb7d27a2f69f5948fa8c301de30f5c8132) Signed-off-by: Matt Madison Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

goarch.bbclass: disable shared runtime for nativesdk builds

2018-03-06T14:43:10+00:00

While useful on embedded devices for saving disk space, use of shared runtime in Go is not the usual practice, so disable it for nativesdk builds. We don't use it for native builds, either, so this makes the SDK match the native environment more closely. (From OE-Core rev: fde7017f9735c0d317023022817b28771df53109) Signed-off-by: Matt Madison Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

go: set GOMIPS envrionment variable

2018-03-06T14:43:10+00:00

Go 1.10 adds support for selecting hard/soft float object code through the GOMIPS environment variable. (From OE-Core rev: f3cabc92dca3408da18f04e4af4051fba1f63c14) Signed-off-by: Matt Madison Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

classes/recipes: Convert SkipPackage -> SkipRecipe

2018-01-26T13:09:09+00:00

The new name is much more consistent with what this actually means. We put the pieces in place to rename everything a while back but looks like we forgot to actually do it! Fix that now. (From OE-Core rev: af9612f5d6b848fceea22d10ee964437299be776) Signed-off-by: Richard Purdie