summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStefan Agner <stefan.agner@toradex.com>2019-10-11 11:25:03 +0200
committerMax Krummenacher <max.krummenacher@toradex.com>2020-02-17 14:52:24 +0100
commit190b7fd6a6092ff248d47da373933be3aadbe2a2 (patch)
tree8d84cefa3b5a159ea62cc2e3b563534131203e63
parentab0bca582337022fbc6763ce43013ce3baa96208 (diff)
conf/local.conf: store uninative tarball in tmp
Store uninative tarball in tmp to work around a race condition seen with multiple builds in parallel. Signed-off-by: Stefan Agner <stefan.agner@toradex.com> Ported from toradex-torizon-manifest, commit 78ad9ee Note that this workaround is no longer needed after with zeus. Signed-off-by: Max Krummenacher <max.krummenacher@toradex.com>
-rw-r--r--buildconf/local.conf6
1 files changed, 6 insertions, 0 deletions
diff --git a/buildconf/local.conf b/buildconf/local.conf
index 47abc94..6b859b2 100644
--- a/buildconf/local.conf
+++ b/buildconf/local.conf
@@ -75,6 +75,12 @@ MACHINE ?= "colibri-imx6"
DL_DIR ?= "${TOPDIR}/../downloads"
#
+# It seems that uninative is racy when building multiple builds in parallel.
+# Work around by storing the uninative tarball in a per-build location.
+#
+UNINATIVE_DLDIR = "${TMPDIR}/uninative/"
+
+#
# Where to place shared-state files
#
# BitBake has the capability to accelerate builds based on previously built output.