summaryrefslogtreecommitdiff
path: root/meta/recipes-devtools/go/go-native.inc
diff options
context:
space:
mode:
authorPatrick Ohly <patrick.ohly@intel.com>2017-04-11 20:38:38 +0200
committerRichard Purdie <richard.purdie@linuxfoundation.org>2017-04-12 15:02:13 +0100
commit39bfa0dd3237cbca47e7fca1075d521f9d073f25 (patch)
tree53f3dfa52fd77c82d225e3a24918be14502a0c15 /meta/recipes-devtools/go/go-native.inc
parentf346473a4868563db7fb63665e808c3fe25a8b58 (diff)
downloadopenembedded-core-39bfa0dd3237cbca47e7fca1075d521f9d073f25.tar.gz
openembedded-core-39bfa0dd3237cbca47e7fca1075d521f9d073f25.tar.bz2
openembedded-core-39bfa0dd3237cbca47e7fca1075d521f9d073f25.zip
recipes/*-cross recipes: ignore TARGET_ARCH sstate hash
"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. Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/go/go-native.inc')
0 files changed, 0 insertions, 0 deletions