summaryrefslogtreecommitdiffstats
path: root/meta-yocto-bsp/conf/machine
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2018-09-07 17:41:27 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-09-10 12:13:38 +0100
commit530aceebc1743b6e279bf9d1c13c841739b6bb14 (patch)
treece1124ad16dcd44418e25e6836b92f489ed38f79 /meta-yocto-bsp/conf/machine
parent479a059c96882817a7f7b3765257f7acdf112348 (diff)
downloadpoky-530aceebc1743b6e279bf9d1c13c841739b6bb14.tar.gz
bitbake: runqueue: Ensure setscene tasks that aren't covered get built
Running "bitbake gconf-native -c cleansstate; bitbake core-image-sato:do_populate_sdk" results in a build where it fails to find gconf-native and fails to build it, merrily trying to build the SDK without gconf being present. The issue is the missing setscene tasks are effectively ignored as the later code in runqueue thinks that since other sstate tasks are present, these 'cover' the missing one. In reality we need to call BB_SETSCENE_DEPVALID to make that decision. To do that we need a "reduced" setscene dependency graph which we don't have in main task graph context. Since that was already done in setscene, we should just assume anything in the non-covered list needs to be built. (Bitbake rev: 464d0339add15bc8b4344ddd1e4c49706e3c0a02) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-yocto-bsp/conf/machine')
0 files changed, 0 insertions, 0 deletions