summaryrefslogtreecommitdiffstats
path: root/meta/lib/oe/classutils.py
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2021-09-28 17:59:09 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2021-10-02 23:09:22 +0100
commit1b3415acd28d2184a95a2bb05ecd4413bd060f35 (patch)
tree3c9ed13bca13f4ce6176534c49f6eae57e800bb5 /meta/lib/oe/classutils.py
parent830059cdeb6396dd2e6766f6053ce3b39dc0b7bb (diff)
downloadpoky-1b3415acd28d2184a95a2bb05ecd4413bd060f35.tar.gz
sstatesig: Revert "Test cross/native hashserv method extension"
This reverts commit 2a76082363d189880613765ad339718e3614049d. We have an issue where x86 host builds are not matching hashes with aarch64 host builds. We'd expect that for a given target, the target artefacts should work regardless of the host architecture, compiler version etc. but this isn't happening and the hashes are differing. This is due to issues from hash equivalence. I believe the commit being reverted was added as a test and there were other fixes at the time which resolved these issues. As illustration of that, different gcc versions are not cauing issues with hash equivalence. That should be similar to the aarch64 case vs. x86-64 and hence if we're not seeing gcc verison issues, we also don't need this special case. As such, revert it as we don't need it and it is in fact breaking sstate reuse cross platform. [YOCTO #14578] (From OE-Core rev: be67dc551ca15a6f19855e8e99848aab2a33800d) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/lib/oe/classutils.py')
0 files changed, 0 insertions, 0 deletions