summaryrefslogtreecommitdiffstats
path: root/meta-yocto-bsp/recipes-kernel
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2020-04-30 20:55:39 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2020-05-02 09:08:52 +0100
commitb55f765ae46eb08d9c92a862c6bc4b9044c0b42d (patch)
tree414edc1ba66def415e5950a0ad62b97f84f488aa /meta-yocto-bsp/recipes-kernel
parent13297d85890ef733d9366f18b40715053bd30829 (diff)
downloadpoky-b55f765ae46eb08d9c92a862c6bc4b9044c0b42d.tar.gz
abi_version/staging: Bump versions to force rebuild after sstate corruption
A "broken" buildtools-extended-tarball has been released into the wild where it is optimising binaries for the host processsor. This is fine in local usage but in a non-homogeneous cluster like our autobuilder, this results in SIGILL on other machines when the sstate is shared amongst them and is painful to debug. The buildtools tarball has been fixed but we need to invalidate the hash equivalence and sstate data. This change does that. Adding to OE-Core rather than autobuilder local changes as its good to illustrate how to do this and the issue is potentially wider than just Yocto Project infrastructure. (From OE-Core rev: 23cdfa9eb23146a69edb77a83ef03719a62ddaae) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-yocto-bsp/recipes-kernel')
0 files changed, 0 insertions, 0 deletions