From: Richard Purdie Date: Tue, 10 Jan 2023 16:00:18 +0000 (+0000) Subject: uninative: Ensure uninative is enabled in all cases for BuildStarted event X-Git-Tag: lucaceresoli/bug-15201-perf-libtraceevent-missing~2019 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=db743cc78fe5172bb4a4dac9c1dad4f5aa9e1491;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git uninative: Ensure uninative is enabled in all cases for BuildStarted event Recent changes in bitbake mean the datastore is not always reset between ConfigParsed and BuildStarted. This means in a fresh buiild, with memory resident bitbake active, uninative may end up disabled. Update the code so the enable code is always run at BuildStarted if needed. Signed-off-by: Richard Purdie --- diff --git a/meta/classes-global/uninative.bbclass b/meta/classes-global/uninative.bbclass index 42c5f8fdf2e..366f7ac7935 100644 --- a/meta/classes-global/uninative.bbclass +++ b/meta/classes-global/uninative.bbclass @@ -40,6 +40,8 @@ python uninative_event_fetchloader() { with open(loaderchksum, "r") as f: readchksum = f.read().strip() if readchksum == chksum: + if "uninative" not in d.getVar("SSTATEPOSTUNPACKFUNCS"): + enable_uninative(d) return import subprocess