From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: flocirel@gmail.com, Andrei Gherzan <andrei.gherzan@windriver.com>
Subject: Re: [PATCH] bzip2-full-native: Remove PROVIDES_append_virtclass-native and modify python-native DEPENDS.
Date: Thu, 26 Jan 2012 20:18:30 +0000 [thread overview]
Message-ID: <1327609110.19643.400.camel@ted> (raw)
In-Reply-To: <1327593042-1252-1-git-send-email-andrei@gherzan.ro>
On Thu, 2012-01-26 at 17:50 +0200, Andrei Gherzan wrote:
> From: Andrei Gherzan <andrei.gherzan@windriver.com>
>
> There are no more -full-native virtclass-native in yocto. The only dependency for this is in
> python where DEPENDS was changed accordingly.
>
> Signed-off-by: Andrei Gherzan <andrei@gherzan.ro>
> ---
> .../recipes-devtools/python/python-native_2.7.2.bb | 2 +-
> meta/recipes-extended/bzip2/bzip2_1.0.6.bb | 1 -
> 2 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/meta/recipes-devtools/python/python-native_2.7.2.bb b/meta/recipes-devtools/python/python-native_2.7.2.bb
> index 8bf0af0..5e99a42 100644
> --- a/meta/recipes-devtools/python/python-native_2.7.2.bb
> +++ b/meta/recipes-devtools/python/python-native_2.7.2.bb
> @@ -1,5 +1,5 @@
> require python.inc
> -DEPENDS = "openssl-native bzip2-full-native zlib-native readline-native sqlite3-native"
> +DEPENDS = "openssl-native bzip2-native zlib-native readline-native sqlite3-native"
> PR = "${INC_PR}.3"
>
> SRC_URI += "file://04-default-is-optimized.patch \
> diff --git a/meta/recipes-extended/bzip2/bzip2_1.0.6.bb b/meta/recipes-extended/bzip2/bzip2_1.0.6.bb
> index 14cd240..23b2bdb 100644
> --- a/meta/recipes-extended/bzip2/bzip2_1.0.6.bb
> +++ b/meta/recipes-extended/bzip2/bzip2_1.0.6.bb
> @@ -28,5 +28,4 @@ do_configure_prepend () {
> cp ${STAGING_DATADIR_NATIVE}/automake*/install-sh ${S}/
> }
>
> -PROVIDES_append_virtclass-native = " bzip2-full-native"
> BBCLASSEXTEND = "native"
There is a reason for this.
It was due to the bzip2 host dependencies on some systems being broken
and requiring that we build our own to ensure we don't hit issues with
bzip2 when unpacking certain recipes. If I recall correctly, its near
impossible to trigger bzip2-native to build without that PROVIDES since
bzip2-native is in ASSUME_PROVIDED.
What was your reason for changing this?
Cheers,
Richard
prev parent reply other threads:[~2012-01-26 20:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 15:50 [PATCH] bzip2-full-native: Remove PROVIDES_append_virtclass-native and modify python-native DEPENDS Andrei Gherzan
2012-01-26 20:18 ` 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=1327609110.19643.400.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=andrei.gherzan@windriver.com \
--cc=flocirel@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox