From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1Stl5c-0006V2-MG for openembedded-core@lists.openembedded.org; Tue, 24 Jul 2012 21:48:16 +0200 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q6OJ8Hdm000679 for ; Tue, 24 Jul 2012 20:08:17 +0100 Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 30630-10 for ; Tue, 24 Jul 2012 20:08:13 +0100 (BST) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q6OJ865t000673 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 24 Jul 2012 20:08:08 +0100 Message-ID: <1343156885.22222.21.camel@ted> From: Richard Purdie To: Patches and discussions about the oe-core layer Date: Tue, 24 Jul 2012 20:08:05 +0100 In-Reply-To: <500EEA46.9000507@windriver.com> References: <1343137799-12032-1-git-send-email-yao.zhao@windriver.com> <1343144070.22222.14.camel@ted> <500EC6B0.60103@windriver.com> <500EEA46.9000507@windriver.com> X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Subject: Re: [PATCH] bzip2-native: fix problems when bzip2-native is installed in parallel X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jul 2012 19:48:16 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Tue, 2012-07-24 at 14:32 -0400, Yao Zhao wrote: > 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 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? See my other reply but I think its libbz2 that it wants. Cheers, Richard