diff options
| author | Marta Rybczynska <rybczynska@gmail.com> | 2022-02-21 18:44:59 +0100 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2022-02-21 23:37:26 +0000 |
| commit | da4c443ac5ae7024d053f7e224c576f750a90085 (patch) | |
| tree | 96e49098ad2fdeda27b9644828b9df0297409960 /bitbake/bin/bitbake | |
| parent | f7fccbe289c216b5bee7336d433589192f9cb6b0 (diff) | |
| download | poky-da4c443ac5ae7024d053f7e224c576f750a90085.tar.gz | |
bitbake: lib/bb: fix exit when found renamed variables
Until now, if a renamed variable was found, bitbake exited
immediately if it was in a class, but continued after an error
message if the variable was in a recipe. This was caused by
cookerdata.py CookerDataBuilder::parseBaseConfiguration checking
a different DataSmart instance than the variable was set in.
To solve the issue, add a special variable and set it when we
find a renamed variable. Check for it in ast.py and bail out
if needed.
(Bitbake rev: d12400600e30549c88dc9e7883dc3d63b1dc1117)
Signed-off-by: Marta Rybczynska <marta.rybczynska@huawei.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'bitbake/bin/bitbake')
0 files changed, 0 insertions, 0 deletions