[OE-core] [PATCH 3/5] classes/externalsrc: handle tasks with existing lockfiles
Paul Eggleton
paul.eggleton at linux.intel.com
Wed Jun 17 17:23:25 UTC 2015
We need to ensure we add a leading space to the value we are prepending
here in case lockfiles already has a value.
Fixes [YOCTO #7813].
Signed-off-by: Paul Eggleton <paul.eggleton at linux.intel.com>
---
meta/classes/externalsrc.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/externalsrc.bbclass b/meta/classes/externalsrc.bbclass
index 75bdb7a..8f7f479 100644
--- a/meta/classes/externalsrc.bbclass
+++ b/meta/classes/externalsrc.bbclass
@@ -55,7 +55,7 @@ python () {
bb.build.deltask(task, d)
else:
# Since configure will likely touch ${S}, ensure only we lock so one task has access at a time
- d.appendVarFlag(task, "lockfiles", "${S}/singletask.lock")
+ d.appendVarFlag(task, "lockfiles", " ${S}/singletask.lock")
# We do not want our source to be wiped out, ever (kernel.bbclass does this for do_clean)
cleandirs = d.getVarFlag(task, 'cleandirs', False)
--
2.1.0
More information about the Openembedded-core
mailing list