From: Yao Zhao <yao.zhao@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Phil Blundell <philb@gnu.org>
Subject: Re: [PATCH] bzip2-native: fix problems when bzip2-native is installed in parallel
Date: Tue, 24 Jul 2012 11:45:16 -0400 [thread overview]
Message-ID: <500EC30C.30503@windriver.com> (raw)
In-Reply-To: <1343144355.5878.18.camel@phil-desktop>
On 12-07-24 11:39 AM, Phil Blundell wrote:
> On Tue, 2012-07-24 at 09:49 -0400, Yao Zhao 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.
> Can the makefile not be fixed to get libbz2.so.0 installed before bzip?
In the Makefile, libbz2.so.0 is installed before bzip2, but the
installation is "make -j xxx install". Then this could happen.
yao
> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-07-24 15:57 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
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 [this message]
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=500EC30C.30503@windriver.com \
--to=yao.zhao@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=philb@gnu.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