Also add Richard.

On 2019-10-11 11:06, Stefan Agner wrote:
> From: Stefan Agner <stefan.ag...@toradex.com>
> 
> In case multiple builds share UNINATIVE_DLDIR's location, one build
> might be in the process of downloading the tarball while another is
> just checking whether the tarball exists. Check for the done file
> instead and rely on the fetchers lockfile mechanism in case two
> builds are running.
> 
> Signed-off-by: Stefan Agner <stefan.ag...@toradex.com>
> ---
>  meta/classes/uninative.bbclass | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/meta/classes/uninative.bbclass b/meta/classes/uninative.bbclass
> index 3326c0db3d..9f8645a36a 100644
> --- a/meta/classes/uninative.bbclass
> +++ b/meta/classes/uninative.bbclass
> @@ -45,7 +45,7 @@ python uninative_event_fetchloader() {
>          tarballdir = os.path.join(d.getVar("UNINATIVE_DLDIR"), chksum)
>          tarballpath = os.path.join(tarballdir, tarball)
>  
> -        if not os.path.exists(tarballpath):
> +        if not os.path.exists(tarballpath + ".done"):
>              bb.utils.mkdirhier(tarballdir)
>              if d.getVar("UNINATIVE_URL") == "unset":
>                  bb.fatal("Uninative selected but not configured,
> please set UNINATIVE_URL")
> -- 
> 2.20.1
-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to