From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: yocto@yoctoproject.org
Subject: [layerindex-web][PATCH] local.conf: fix HOSTTOOLS blocking parsing
Date: Mon, 20 Mar 2017 14:27:31 +1300 [thread overview]
Message-ID: <20170320012731.10119-1-paul.eggleton@linux.intel.com> (raw)
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@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
reply other threads:[~2017-03-20 1:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170320012731.10119-1-paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.