This bug was originally reported by Peter here: https://lists.openembedded.org/g/openembedded-core/message/197092. But since the right solution is not found yet it might be better to track this as a bug.

Following workflow is broken when built from sstate-cache:
https://docs.yoctoproject.org/singleindex.html#setting-up-the-extensible-sdk-environment-directly-in-a-yocto-build
This is already broken in kirkstone.

Reproducer:
$ bitbake meta-ide-support && bitbake build-sysroots -c build_native_sysroot
$ ls -1 build/tmp/sysroots/*/*gdb-cross* && echo OK || echo FAIL #succeeds from scratch
build/tmp/sysroots/x86_64/manifest-x86_64-gdb-cross-x86_64.populate_sysroot
OK
$ rm -rf build/tmp
$ bitbake meta-ide-support && bitbake build-sysroots -c build_native_sysroot
$ ls -1 build/tmp/sysroots/*/*gdb-cross* && echo OK || echo FAIL #fails from sstate-cache
ls: cannot access 'build/tmp/sysroots/*/*gdb-cross*': No such file or directory
FAIL

build-sysroot populates sysroot with recipes which run populate_sysroot or populate_sysroot_setscene. Dependency on its own populate_sysroot does not seem to work when building from sstate-cache as this task is not executed. This seem to becaused by inheriting nopackages class which deletes tasks thus messing the setscene dependencies.