summaryrefslogtreecommitdiffstats
path: root/meta/recipes-devtools/gdb/gdb-cross_7.12.1.bb
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:09:58 +0100
commit3e903cb42f94c77900115035155cd62142d29544 (patch)
treebecda59570181b9a3b2081297565babbc14d964e /meta/recipes-devtools/gdb/gdb-cross_7.12.1.bb
parentfc43f10a517d5fb27145b796471d27419ef1fd19 (diff)
downloadpoky-3e903cb42f94c77900115035155cd62142d29544.tar.gz
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. (From OE-Core rev: 39bfa0dd3237cbca47e7fca1075d521f9d073f25) Signed-off-by: Patrick Ohly <patrick.ohly@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-devtools/gdb/gdb-cross_7.12.1.bb')
0 files changed, 0 insertions, 0 deletions