From: Yao Zhao <yao.zhao@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: bzip2-native problem
Date: Wed, 18 Jul 2012 11:02:54 -0400 [thread overview]
Message-ID: <5006D01E.2080409@windriver.com> (raw)
Hi all,
Got a problem about bzip2-native:
The reason is that when unpacking xextproto-7.2.0.tar.bz2,
bzip2-native's build is triggered too because of another package's
dependency. And loader can't find libbz2.so.0 which is in sysroot(host
bzip2 used libbz2.so.1 so it is sure the libbz2.so.0 in sysroot) I have
searched the paths in PATH below and only find bzip2 in 2 places: host
/bin/bzip2 and sysroot bzip2.
In bzip2's Makefile, the install is make -j xxx ... although the install
is first to install libbz2.so.0 then bzip2 but because of the "-j xxx"
so it is possible that bzip2 is installed first but libbz2.so.0 is not
ready yet(in a subshell this link is created).
So I have to make the install atomic or at least don't install in parallel.
so there are a couple of workarounds:
1.set PARALLEL_MAKEINST="" (one line change, and only one library, 2
binaries installed(bzip2, bzip2recover) + 3 scripts + a couple of links)
2.make a statically linked bzip2 and bzip2recover
3.like perl or python native to make a bzip2-native subdir in sysroot
then only packages explicitly inherit bzip2native which will set the path.
I need your advice!
thanks,
yao
Here is the tail of log.do_unpack.6884:
--------------------------------------------------
DEBUG: SITE files ['endian-big', 'bit-32', 'powerpc-common', 'common-linux', 'common-glibc', 'powerpc32-linux', 'powerpc-linux', 'common']
DEBUG: Executing shell function wrl_buildlink
DEBUG: Shell function wrl_buildlink finished
DEBUG: Executing python function do_unpack
DEBUG: Executing python function base_do_unpack
NOTE: Unpacking /builds-2012-07-13-001944/fsl-p4080_std_tc/bitbake_build/downloads/xextproto-7.2.0.tar.bz2 to /builds-2012-07-13-001944/fsl-p4080_std_tc/bitbake_build/tmp/work/ppce500mc-wrs-linux/xextproto-1_7.2.0-r0/
bzip2: error while loading shared libraries: libbz2.so.0: cannot open shared object file: No such file or directory
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
DEBUG: Python function base_do_unpack finished
DEBUG: Python function do_unpack finished
ERROR: Function failed: Unpack failure for URL: 'http://xorg.freedesktop.org/releases/individual/proto/xextproto-7.2.0.tar.bz2'. Unpack command PATH="/builds-2012-07-13-001944/fsl-p4080_std_tc/layers/oe-core/scripts:/builds-2012-07-13-001944/fsl-p4080_std_tc/bitbake_build/tmp/sysroots/x86_64-linux/usr/bin/ppce500mc-wrs-linux:/builds-2012-07-13-001944/fsl-p4080_std_tc/bitbake_build/tmp/sysroots/fsl-p4080/usr/bin/crossscripts:
/builds-2012-07-13-001944/fsl-p4080_std_tc/bitbake_build/tmp/sysroots/x86_64-linux/usr/sbin:/builds-2012-07-13-001944/fsl-p4080_std_tc/bitbake_build/tmp/sysroots/x86_64-linux/usr/bin:/builds-2012-07-13-001944/fsl-p4080_std_tc/bitbake_build/tmp/sysroots/x86_64-linux/sbin:/builds-2012-07-13-001944/fsl-p4080_std_tc/bitbake_build/tmp/sysroots/x86_64-linux//bin:/builds-2012-07-13-001944/fsl-p4080_std_tc/bitbake_build/bin:/ba2/yow
-blade16.2/builds-2012-07-13-001944/fsl-p4080_std_tc/layers/oe-core/scripts:/builds-2012-07-13-001944/fsl-p4080_std_tc/bitbake/bin/:/wrlinux-x/layers/wrlinux/scripts:/builds-2012-07-13-001944/fsl-p4080_std_tc/scripts:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/builds-2012-07-13-001944/fsl-p4080_std_tc/layers/local/scripts:/wrlinux-x/layers/wrlinux/scripts:/wrlinux-x/layers/wrlcompat/sc
ripts" bzip2 -dc /builds-2012-07-13-001944/fsl-p4080_std_tc/bitbake_build/downloads/xextproto-7.2.0.tar.bz2 | tar x --no-same-owner -f - failed with return value 2
next reply other threads:[~2012-07-18 19:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 15:02 Yao Zhao [this message]
2012-07-20 16:25 ` bzip2-native problem 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=5006D01E.2080409@windriver.com \
--to=yao.zhao@windriver.com \
--cc=openembedded-devel@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