From 68684b4903261cc5d3f48355f7cc6671484bb546 Mon Sep 17 00:00:00 2001 From: Bruce Ashfield Date: Wed, 21 Dec 2011 15:00:02 -0500 Subject: linux-yocto: use PATH to locate kconf_check 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 --- meta/classes/kernel-yocto.bbclass | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/meta/classes/kernel-yocto.bbclass b/meta/classes/kernel-yocto.bbclass index 79f82e3513..f78caaf23c 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 ) -- cgit v1.2.3