Bug 13968 - variables in BB_HASHBASE_WHITELIST built from non-whitelisted variables should trigger a warning
Summary: variables in BB_HASHBASE_WHITELIST built from non-whitelisted variables shoul...
Status: RESOLVED WORKSFORME
Alias: None
Product: BitBake
Classification: Build System, Metadata & Runtime
Component: bitbake (show other bugs)
Version: unspecified
Hardware: x86 Multiple
: Medium normal
Target Milestone: 3.4
Assignee: Richard Purdie
QA Contact:
URL:
Whiteboard:
Depends on:
Blocks:
 
Reported: 2020-07-03 04:33 UTC by Yann Dirson
Modified: 2021-04-20 13:08 UTC (History)
3 users (show)

See Also:
OS type for building Yocto: ---
Type of Regression: ---
Verified:
Documentation change: No (bug/feature does not impact docs)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Yann Dirson 2020-07-03 04:33:46 UTC 
https://github.com/rockchip-linux/meta-rockchip/ demonstrates the issue:

conf/layer.conf:RK_LICENSE_PATH = "${LAYERDIR}/files/custom-licenses"
conf/layer.conf:RK_BINARY_LICENSE = "${RK_LICENSE_PATH}/LICENSE.rockchip"
conf/layer.conf:LICENSE_PATH += "${RK_LICENSE_PATH}"

This causes task hashes to change when building in a different location because RK_LICENSE_PATH then changes.  Obviously an oversight, and bitbabke shoule be
able to warn about this case.
Comment 1 Randy MacLeod 2020-07-09 07:45:58 UTC 
yocto-check-layer does this already.
Comment 2 Richard Purdie 2021-04-20 13:08:17 UTC 
If you run our check-layer script this will be highlighted. It is hard for bitbake to test without having two runs to compare. If you have a proposal on how to make bitbake detect the change generically I'm open to ideas but I can't see an easy way to have this work "out the box". Hard to know what to mark this as in bugzilla, going for worksforme which isn't quite right but...