From b236454b8398ebb9dbd535158d608c8d238fe070 Mon Sep 17 00:00:00 2001 From: Stefan Agner Date: Fri, 11 Oct 2019 11:06:59 +0200 Subject: uninative: check .done file instead of tarball 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. (From OE-Core rev: a1c95580549cb4f77601e62c7f026b19c752d853) Signed-off-by: Stefan Agner Signed-off-by: Richard Purdie --- meta/classes/uninative.bbclass | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'meta/classes') 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") -- cgit v1.2.3-54-g00ecf