From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jeff Polk <jeff.polk@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] sanity.bbclass: add xz to SANITY_REQUIRED_UTILITIES
Date: Mon, 09 Sep 2013 23:20:03 +0100 [thread overview]
Message-ID: <1378765203.3484.148.camel@ted> (raw)
In-Reply-To: <1378744154-6489-1-git-send-email-jeff.polk@windriver.com>
On Mon, 2013-09-09 at 11:29 -0500, Jeff Polk wrote:
> xz is commonly available and is now used by some recipes
> It's reasonable to expect it to be present so error immediately
> if it's not.
>
> Signed-off-by: Jeff Polk <jeff.polk@windriver.com>
> ---
> meta/classes/sanity.bbclass | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Is it in all the base distros we use as standard or do we need update
the quickstart? Shouldn't we also be adding it to ASSUME_PROVIDED?
I think there is a different bug which may sometimes lead to build
failures due to the dependency on it not being generated correctly.
Cheers,
Richard
> diff --git a/meta/classes/sanity.bbclass b/meta/classes/sanity.bbclass
> index a49b405..26038cb 100644
> --- a/meta/classes/sanity.bbclass
> +++ b/meta/classes/sanity.bbclass
> @@ -2,7 +2,7 @@
> # Sanity check the users setup for common misconfigurations
> #
>
> -SANITY_REQUIRED_UTILITIES ?= "patch diffstat makeinfo git bzip2 tar gzip gawk chrpath wget cpio"
> +SANITY_REQUIRED_UTILITIES ?= "patch diffstat makeinfo git bzip2 tar gzip gawk chrpath wget cpio xz"
>
> def bblayers_conf_file(d):
> return os.path.join(d.getVar('TOPDIR', True), 'conf/bblayers.conf')
prev parent reply other threads:[~2013-09-09 22:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-09 16:29 [PATCH] sanity.bbclass: add xz to SANITY_REQUIRED_UTILITIES Jeff Polk
2013-09-09 22:20 ` Richard Purdie [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1378765203.3484.148.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=jeff.polk@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.