3e903cb42f
"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 <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> |
||
---|---|---|
.. | ||
go-1.4 | ||
go-1.6 | ||
go-1.7 | ||
go-1.8 | ||
go-1.4.inc | ||
go-1.6.inc | ||
go-1.7.inc | ||
go-1.8.inc | ||
go-bootstrap-native_1.4.bb | ||
go-common.inc | ||
go-cross.inc | ||
go-cross_1.7.bb | ||
go-cross_1.8.bb | ||
go-native.inc | ||
go-native_1.8.bb | ||
go.inc | ||
go_1.6.bb | ||
go_1.7.bb | ||
go_1.8.bb |