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 <[email protected]> --- meta/recipes-bsp/u-boot/u-boot.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/recipes-bsp/u-boot/u-boot.inc b/meta/recipes-bsp/u-boot/u-boot.inc index 6bbe457..769c941 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 ${MACHINE} machine configuration.") } # Allow setting an additional version string that will be picked up by the -- 1.7.10.4 _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
