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 ]

(From OE-Core master rev: beef66beaee926ec3d3640b79133fdb2ccc404f0)

(From OE-Core rev: 0042a3230a0c3b983245aabad6fdc3b3d3fcc2cd)

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Ross Burton
2013-08-01 11:07:36 +01:00
committed by Richard Purdie
parent bc5e808f01
commit baffd936a5

View File

@@ -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))
}
# Some versions of u-boot use .bin and others use .img. By default use .bin