]> code.ossystems Code Review - openembedded-core.git/commitdiff
linux-yocto: use PATH to locate kconf_check
authorBruce Ashfield <bruce.ashfield@windriver.com>
Wed, 21 Dec 2011 20:00:02 +0000 (15:00 -0500)
committerSaul Wold <sgw@linux.intel.com>
Tue, 3 Jan 2012 04:26:06 +0000 (20:26 -0800)
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.ashfield@windriver.com>
meta/classes/kernel-yocto.bbclass

index 79f82e3513a1e4fe7563f57abbb8df14f95b7fce..f78caaf23c0949a2848686f61f64092758e83bd4 100644 (file)
@@ -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 )