From: Bruce Ashfield <bruce.ashfi...@windriver.com>
The changes made to prefer in-tree kernel tools forced the location
of kconf_check prematurely. For maximum flexibility, locating it
on the PATH is ideal, since the transition to in-tree tools will be
completely transparent.
Signed-off-by: Bruce Ashfield <bruce.ashfi...@windriver.com>
---
meta/classes/kernel-yocto.bbclass | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/classes/kernel-yocto.bbclass
b/meta/classes/kernel-yocto.bbclass
index 79f82e3..f78caaf 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -124,8 +124,8 @@ python do_kernel_configcheck() {
bb.plain("NOTE: validating kernel configuration")
- pathprefix = "export PATH=%s; " % d.getVar('PATH', True)
- cmd = bb.data.expand("cd ${B}/..; ${S}/scripts/util/kconf_check -config-
${B} ${S} ${B} ${KBRANCH}",d )
+ pathprefix = "export PATH=%s:%s; " % (d.getVar('PATH', True),
"${S}/scripts/util/")
+ cmd = bb.data.expand("cd ${B}/..; kconf_check -config- ${B} ${S} ${B}
${KBRANCH}",d )
ret, result = commands.getstatusoutput("%s%s" % (pathprefix, cmd))
bb.plain( "%s" % result )
--
1.7.6.4
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
