Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Yao Zhao <yao.zhao@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bzip2-native: fix problems when bzip2-native is installed in parallel
Date: Tue, 24 Jul 2012 14:32:38 -0400	[thread overview]
Message-ID: <500EEA46.9000507@windriver.com> (raw)
In-Reply-To: <500EC6B0.60103@windriver.com>

On 12-07-24 12:00 PM, Yao Zhao wrote:
> On 12-07-24 11:34 AM, Richard Purdie wrote:
>> On Tue, 2012-07-24 at 14:57 +0100, Burton, Ross wrote:
>>> On 24 July 2012 14:49, Yao Zhao <yao.zhao@windriver.com> wrote:
>>>> when bzip2-native is installed in parallel to sysroot, it is 
>>>> possible that
>>>> some packages are using bzip2 to unpack, there are chances that 
>>>> bzip2 is
>>>> installed to sysroot but libbz2.so.0 not installed yet because 
>>>> parallel
>>>> installation.
>>>> link bzip2 and bzip2recover statically to avoid this problem and 
>>>> don't lose
>>>> parallel installation. libbz2.so is still available.
>>> Is it me, or is this officially getting silly?  This probably happens
>>> for *every* binary in the sysroot that links to a library, which is
>>> probably a fair proportion of them.  Statically linking every single
>>> one and then special-casing further problems where a static link isn't
>>> sufficient (see pythonnative) just isn't going to scale.
>> It happens for things in ASSUME_PROVIDED so there is only a finite list
>> of these issues. I'm curious what is actually triggering bzip2-native to
>> build given its in ASSUME_PROVIDED...
> Yeah, it is in the ASSUME_PROVIDED but somehow it was built too. I 
> will take a further look at why it was built.
>
It seems that python-native is depending on "bzip2-full-native" and 
bzip2 does provide this "bzip2-full-native".
Change it from "bzip2-full-native" to "bzip2-native" , bzip2-native is 
not built any more. The code may not check the
Why we need the bzip2-full-native? any idea?

thanks,
yao
> thanks,
> yao
>> Cheers,
>>
>> Richard
>>
>>
>> _______________________________________________
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core





  reply	other threads:[~2012-07-24 18:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24 13:49 [PATCH] bzip2-native: fix problems when bzip2-native is installed in parallel Yao Zhao
2012-07-24 13:57 ` Burton, Ross
2012-07-24 14:01   ` Yao Zhao
2012-07-24 15:34   ` Richard Purdie
2012-07-24 16:00     ` Yao Zhao
2012-07-24 18:32       ` Yao Zhao [this message]
2012-07-24 19:08         ` Richard Purdie
2012-07-24 18:39   ` Mark Hatle
2012-07-24 19:07     ` Richard Purdie
2012-07-24 19:25       ` Yao Zhao
2012-07-24 19:32         ` Richard Purdie
2012-07-25 20:07           ` Yao Zhao
2012-07-24 15:39 ` Phil Blundell
2012-07-24 15:45   ` Yao Zhao
2012-07-24 15:47     ` Phil Blundell
2012-07-24 16:39       ` Yao Zhao
2012-07-24 16:52         ` Mark Hatle
2012-07-24 17:03           ` Yao Zhao

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=500EEA46.9000507@windriver.com \
    --to=yao.zhao@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox