From: Robert Yang <liezhi.yang@windriver.com>
To: "Burton, Ross" <ross.burton@intel.com>,
Andre McCurdy <armccurdy@gmail.com>
Cc: OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bzip2: set correct soname
Date: Thu, 7 Apr 2016 10:37:18 +0800 [thread overview]
Message-ID: <5705C7DE.2000102@windriver.com> (raw)
In-Reply-To: <CAJTo0LZSmc3+nOGn1dK9CzKqd+aAkAnFdk=tkk-gCHPqz+8NNg@mail.gmail.com>
Hi Ross,
I got this error when build in an old build dir:
| pbzip2: error while loading shared libraries: libbz2.so.0: cannot open shared
object file: No such file or directory
| WARNING: exit code 127 from a shell command.
| ERROR: Function failed: do_image_tar (log file is located at
/buildarea/lyang1/test_fetch/tmp/work/qemux86_64-poky-linux/core-image-minimal/1.0-r0/temp/log.do_image_tar.33968)
ERROR: Task 19
(/buildarea/lyang1/poky/meta/recipes-core/images/core-image-minimal.bb,
do_image_tar) failed with exit code '1'
It is OK when clean pbzip2-native and rebuild. But I wonder how can this
happen since pbzip2-native DEPENDS on bzip2-native.
// Robert
On 04/06/2016 04:23 PM, Burton, Ross wrote:
>
> On 5 April 2016 at 23:02, Andre McCurdy <armccurdy@gmail.com
> <mailto:armccurdy@gmail.com>> wrote:
>
> > +libbz2_la_LDFLAGS = -version-info 1:6:0
>
> 1:6:0 or 1:0:6 ?
>
>
> 1:6:0 results in /usr/lib/libbz2.so.1.0.6, which is what upstream intended in
> their broken Makefile that we don't use.
>
> Ross
>
>
next prev parent reply other threads:[~2016-04-07 2:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 21:26 [PATCH] bzip2: set correct soname Ross Burton
2016-04-05 22:02 ` Andre McCurdy
2016-04-06 8:23 ` Burton, Ross
2016-04-07 2:37 ` Robert Yang [this message]
2016-04-07 9:12 ` Burton, Ross
2016-04-07 9:50 ` Robert Yang
2016-04-08 2:59 ` Robert Yang
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=5705C7DE.2000102@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.