diff options
| author | Chris Laplante <chris.laplante@agilent.com> | 2024-12-11 12:41:27 -0500 |
|---|---|---|
| committer | Steve Sakoman <steve@sakoman.com> | 2025-02-12 06:29:33 -0800 |
| commit | c621ccd93bdb4bd72a931426d963c583f6109364 (patch) | |
| tree | c412332f8a71752b5d2fc15c626a6a215aa35176 /meta | |
| parent | 6b2ad54a4381af1c14f6253b62fde6df0964bfe5 (diff) | |
| download | poky-c621ccd93bdb4bd72a931426d963c583f6109364.tar.gz | |
bitbake: cooker: Make cooker 'skiplist' per-multiconfig/mc
Previously, the cooker skiplist was shared across multiconfigs
(including default ''). If you had a recipe that was incompatible with
several multiconfigs for different reasons, then the displayed reason
(i.e. the "ERROR: Nothing PROVIDES" and "* was skipped" messages) might
vary across invocations of bitbake. This was caused by the random order
in which recipes are parsed under different multiconfig contexts, with
each skip reason overwriting the previously assigned reason.
I hit this specificially when using COMPATIBLE_MACHINE, but
COMPATIBLE_HOST (or anything using bb.parse.SkipRecipe) would have done it too.
(Bitbake rev: a8578d12dfe5a3c92119bfee224595a392d6b0dd)
Signed-off-by: Chris Laplante <chris.laplante@agilent.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit c51f01a35ed9a928402eab0899598b5c59602eef)
Signed-off-by: Steve Sakoman <steve@sakoman.com>
Diffstat (limited to 'meta')
0 files changed, 0 insertions, 0 deletions