[OE-core] [PATCH][V2] u-boot: state the MACHINE when skipping u-boot

[Laszlo Papp]

Speaking of gerrit terms: I would prefer that you didn't submit this.

I would like it to be more specific. If it cannot be more specific, it
should provide further information to get more specific information. Note,
machine configuration can be the command line as well, so this would still
be vague.

On Thu, Aug 1, 2013 at 11:07 AM, Ross Burton <ross.burton at intel.com> wrote:

> 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 <ross.burton at intel.com>
> ---
>  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..6ec63df 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
> --
> 1.7.10.4
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core at lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20130801/a73801ec/attachment-0002.html>