[OE-core] [PATCH] uninative: add variables to the whitelist so that it does not re-triger recipe parsing

Khem Raj raj.khem at gmail.com
Fri Mar 16 23:00:57 UTC 2018


On Fri, Mar 16, 2018 at 10:31 AM Cuero Bugot <cbugot at sierrawireless.com>
wrote:

> When uninative is activated (poky's default) internal datastore variables
> are modified (NATIVELSBSTRING and SSTATEPOSTUNPACKFUNCS) to enable uninative
> support. This is happening after parsing is done at the beginning of the
> build. On the next bitbake call the recipe would be parsed if the two
> variables above were not added to the parsing whitelist
> BB_HASHCONFIG_WHITELIST.
>
> The fix is to add these two variables to the recipe parsing whitelist
> BB_HASHCONFIG_WHITELIST, this is done at recipe parsing time, only when
> uninative.bbclass is used.


It seems you have a case where data is already parsed and then uninstive is
enabled after this the reparse is happening. Or is it always happening when
uninative is enabled

>
>
> Signed-off-by: Cuero Bugot <cbugot at sierrawireless.com>
> ---
>  meta/classes/uninative.bbclass | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/meta/classes/uninative.bbclass
> b/meta/classes/uninative.bbclass
> index 8f34483..d1fdbc8 100644
> --- a/meta/classes/uninative.bbclass
> +++ b/meta/classes/uninative.bbclass
> @@ -8,6 +8,9 @@ UNINATIVE_TARBALL ?= "${BUILD_ARCH}-nativesdk-libc.tar.bz2"
>  #UNINATIVE_CHECKSUM[x86_64] = "dead"
>  UNINATIVE_DLDIR ?= "${DL_DIR}/uninative/"
>
> +# Enabling uninative will change the following variables so they need to
> go the parsing white list to prevent multiple recipe parsing
> +BB_HASHCONFIG_WHITELIST += "NATIVELSBSTRING SSTATEPOSTUNPACKFUNCS"
> +
>  addhandler uninative_event_fetchloader
>  uninative_event_fetchloader[eventmask] = "bb.event.BuildStarted"
>
> --
> 2.7.4
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20180316/f5890fcf/attachment-0002.html>


More information about the Openembedded-core mailing list