summaryrefslogtreecommitdiffstats
path: root/recipes-devtools/python
diff options
context:
space:
mode:
authorKhem Raj <khem.raj@oss.qualcomm.com>2026-07-27 10:19:44 -0700
committerKhem Raj <raj.khem@gmail.com>2026-07-27 16:29:54 -0700
commite7ff013afaa78f639a3edf1627ce5c186ad87c0a (patch)
tree4c5f89667d6350b00e1c971efdb65f4353775fd7 /recipes-devtools/python
parent0baedd06e78d26d3b927471cfd91960b7229a178 (diff)
downloadmeta-clang-e7ff013afaa78f639a3edf1627ce5c186ad87c0a.tar.gz
nonclangable.conf: Pin perf via KERNEL_TOOLCHAIN instead of TOOLCHAIN
perf inherits kernel-arch, which since oe-core 0e3756efe0 ("kernel-arch: add KERNEL_TOOLCHAIN to switch the whole kernel toolchain") sets KERNEL_TOOLCHAIN ?= "gcc" TOOLCHAIN = "${KERNEL_TOOLCHAIN}" bitbake's basehash records the unexpanded value of a variable along with its dependency set, not just the final expansion. Overriding TOOLCHAIN here replaced '${KERNEL_TOOLCHAIN}' with the literal 'gcc' and dropped the recorded dependency on KERNEL_TOOLCHAIN, so merely adding this layer changed perf's basehash even though the resulting toolchain is identical. yocto-check-layer flags that as the layer altering OE-Core signatures: AssertionError: Adding layer meta-clang changed signatures. 9 signatures changed [...] List of dependencies for variable TOOLCHAIN changed from 'frozenset({'KERNEL_TOOLCHAIN'})' to 'frozenset()' Dependency on Variable KERNEL_TOOLCHAIN was removed Variable TOOLCHAIN value changed from '${KERNEL_TOOLCHAIN}' to 'gcc' Pin KERNEL_TOOLCHAIN instead. TOOLCHAIN then stays byte-identical to the OE-Core baseline, so the signatures match, while perf is still forced to gcc for anyone setting KERNEL_TOOLCHAIN = "clang". Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Diffstat (limited to 'recipes-devtools/python')
0 files changed, 0 insertions, 0 deletions