From patchwork Thu Dec 22 18:06:00 2011 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [4/4] linux-yocto: use PATH to locate kconf_check Date: Thu, 22 Dec 2011 18:06:00 -0000 From: Bruce Ashfield X-Patchwork-Id: 17515 Message-Id: <906567682d06d8de1915b78ddf6128cd7bda6adc.1324576164.git.bruce.ashfield@windriver.com> To: richard.purdie@linuxfoundation.org Cc: dvhart@linux.intel.com, openembedded-core@lists.openembedded.org, saul.wold@intel.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 --- 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 )