From: Ross Burton Date: Thu, 1 Aug 2013 10:07:36 +0000 (+0100) Subject: u-boot: state the MACHINE when skipping u-boot X-Git-Tag: yocto-4.0~32029 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=beef66beaee926ec3d3640b79133fdb2ccc404f0;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git u-boot: state the MACHINE when skipping u-boot If the user accidently tries building u-boot on a machine doesn't use u-boot (such as qemuarm) the error message doesn't make it clear why u-boot was skipped. To help, state the machine that was being built for again. [ YOCTO #4945 ] Signed-off-by: Ross Burton Signed-off-by: Saul Wold --- diff --git a/meta/recipes-bsp/u-boot/u-boot.inc b/meta/recipes-bsp/u-boot/u-boot.inc index 6bbe457dfa4..6ec63df0e31 100644 --- a/meta/recipes-bsp/u-boot/u-boot.inc +++ b/meta/recipes-bsp/u-boot/u-boot.inc @@ -13,7 +13,7 @@ python () { FILE = os.path.basename(d.getVar("FILE", True)) bb.debug(1, "To build %s, see %s for instructions on \ setting up your machine config" % (PN, FILE)) - raise bb.parse.SkipPackage("because UBOOT_MACHINE is not set") + raise bb.parse.SkipPackage("UBOOT_MACHINE is not set in the %s machine configuration." % d.getVar("MACHINE", True)) } # Allow setting an additional version string that will be picked up by the