[yocto] [layerindex-web][PATCH] local.conf: fix HOSTTOOLS blocking parsing

Paul Eggleton paul.eggleton at linux.intel.com
Sun Mar 19 18:27:31 PDT 2017


In OE-Core master, HOSTTOOLS specifies a list of host-side tools to be
symlinked into a directory that is placed in a filtered path, so that
binaries used from the host are a controlled subset. This variable is
acted upon at configuration parse time and if any tools are missing,
parsing is terminated.

We're not actually running any tasks, so we won't need to call most of
the tools specified by HOSTTOOLS. There is one we definitely do need to
run (gcc) so keep that one, but the rest can be moved to
HOSTTOOLS_NONFATAL.

Signed-off-by: Paul Eggleton <paul.eggleton at linux.intel.com>
---
 conf/local.conf | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/conf/local.conf b/conf/local.conf
index 5a20371..9fe3851 100644
--- a/conf/local.conf
+++ b/conf/local.conf
@@ -10,3 +10,10 @@ MACHINE = "qemux86"
 # OE-Core basic distro configuration
 DISTRO = ""
 
+# We're not doing any building, no need to error on missing host tools,
+# but move them to HOSTTOOLS_NONFATAL just in case any do get called
+# from anonymous python or python expressions
+HOSTTOOLS_NONFATAL := "${@d.getVar('HOSTTOOLS', True) or ''} ${@d.getVar('HOSTTOOLS_NONFATAL', True) or ''}"
+# We do definitely need gcc since populate_sdk_base.bbclass refers to
+# oe.utils.get_gcc_version() in a python expression
+HOSTTOOLS = "gcc"
-- 
2.9.3




More information about the yocto mailing list