linux/poky.git/meta/recipes-devtools/go, branch uninative-1.7

go: centralize definition of COMPATIBLE_HOST

2017-07-27T21:36:52+00:00

Put it in goarch.bbclass which all go related recipes inherit. (From OE-Core rev: 9e899bbc081cb932c1492f6d6802b908d70ef42f) Signed-off-by: Joe Slater Signed-off-by: Richard Purdie

go: do not try to build for powerpc64

2017-06-09T16:12:14+00:00

Add powerpc64 to the incompatible host list. (From OE-Core rev: 358c2daee23eaa778e6a4f356b05b2d5a248fdd1) Signed-off-by: Joe Slater Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

go: Upgrade to 1.8.3

2017-06-05T08:19:51+00:00

Add a comment to fix build musl<->glibc switch while using same TMPDIR (From OE-Core rev: bc940753ee4af8c656f33d63e33c3d12d419446e) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

recipes/*-cross recipes: ignore TARGET_ARCH sstate hash

2017-04-12T14:09:58+00:00

"yocto-compat-layer.py --machines" showed that shared packages like gcc-cross-powerpc64 have a sstate signature that depends on TUNEFLAGS. As a result, there are unnecessary rebuilds and potential conflicts in a multiconfig. That's due to the way how TARGET_ARCH is set. Richard Purdie suggested setting TARGET_ARCH[vardepvalue] as fix, which works. It would be shorter to do that in cross.bbclass instead of repeating the relevant line in different recipes, but Richard was concerned about potential side-effects in other usages of cross.bbclass. TARGET_GOARM as used in go.inc is still causing signature differences for go-cross-powerpc64 and machines b4420qds-64b and p5020ds-64b. This needs further investigation. (From OE-Core rev: 39bfa0dd3237cbca47e7fca1075d521f9d073f25) Signed-off-by: Patrick Ohly Signed-off-by: Richard Purdie

go-cross: avoid libgcc dependency

2017-04-12T14:09:58+00:00

libgcc gets compiled differently depending on the tune flags for the target. That dependency would make go-cross also tune specific and prevent sharing it between different machines using the same architecture. For example, MACHINE=intel-corei7-64 and MACHINE=qemux86-64 shared the same go-cross-x86_64, but compiled libgcc differently. The libgcc dependency gets inherited from go.inc, but does not seem to be necessary for go-cross (compiling go-helloworld still succeeds). The dependency is left in go.inc conditionally, just in case that it really is relevant for the various on-target recipes which inherit that. Because go-cross*.bb includes go*.bb, moving the DEPENDS into a .inc file that only gets included for the target recipes doesn't work. Reshuffling the content of three .bb files seems too intrusive at this point. (From OE-Core rev: 58149a7be4172074349951aaf5af95fa40fd4bdb) Signed-off-by: Patrick Ohly Signed-off-by: Richard Purdie

go-native: Install bootstrap binaries with 1.4 suffix

2017-03-22T11:35:21+00:00

Currently, bin/go and bin/gofmt collide between go-native and go-bootstrap-native packages, these are scripts anyway which call the go compiler proper from right install, in this case create go1.4 and gofmt1.4 names for these scripts to avoid namespace collision (From OE-Core rev: c46faa132d39d3dc235a019d9abf6e46f74e3bae) Signed-off-by: Khem Raj Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

go: Remove mips32r2 from mips

2017-03-17T16:53:05+00:00

mips32r1 is only one supported for mips32 (From OE-Core rev: d39b819579c767aa7892835624540fd6509db201) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

go: Fix packaging for target go

2017-03-17T16:53:04+00:00

We need all packaging tasks when building go for target (From OE-Core rev: 8f504a7737d5e6be6ec61f9ce8728a2c74102a8a) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

go: add native recipes for 1.8

2017-03-14T14:42:18+00:00

(From OE-Core rev: 13a5c3dac4b5b0ccb4c5dfebf79b468acd8e1983) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

go: Enable on musl

2017-03-14T14:42:18+00:00

Working fine for musl targets now (From OE-Core rev: 1bab5be8133f62cdae251e66db6f472c3c37297c) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie