> -Original Message-
> From: Phil Blundell [mailto:p...@pbcl.net]
> Sent: Wednesday, May 15, 2013 1:45 PM
> To: Slater, Joseph
> Cc: Hatle, Mark; openembedded-core@lists.openembedded.org
> Subject: Re: [OE-core] [PATCH 1/1] zlib: put shared libraries in base_libdir
&g
On Wed, 2013-05-15 at 19:50 +, Slater, Joseph wrote:
> Yes, this is it:
>
> WARNING: QA Issue: libpam: /lib64/security/pam_cracklib.so, installed in the
> base_prefix,
> requires a shared library under exec_prefix
> (/usr): libz.so.1 => /usr/lib64/libz.so.1 (0xdead5000)
Presumably pa
[OE-core] [PATCH 1/1] zlib: put shared libraries in base_libdir
>
> On 5/15/13 4:54 AM, Phil Blundell wrote:
> > On Tue, 2013-05-14 at 16:35 -0700, Joe Slater wrote:
> >> We put the shared libraries in base_libdir because at least
> >> one library under base_libdir, p
On 5/15/13 4:54 AM, Phil Blundell wrote:
On Tue, 2013-05-14 at 16:35 -0700, Joe Slater wrote:
We put the shared libraries in base_libdir because at least
one library under base_libdir, pam_cracklib.so, needs them
and will cause a qa warning when it is built.
Which warning are you getting? Fro
On Tue, 2013-05-14 at 16:35 -0700, Joe Slater wrote:
> We put the shared libraries in base_libdir because at least
> one library under base_libdir, pam_cracklib.so, needs them
> and will cause a qa warning when it is built.
Which warning are you getting? From the description it sounds like
unsafe
On 05/15/2013 02:35 AM, Joe Slater wrote:
We put the shared libraries in base_libdir because at least
one library under base_libdir, pam_cracklib.so, needs them
and will cause a qa warning when it is built.
---
meta/recipes-core/zlib/zlib_1.2.7.bb | 14 ++
1 files changed, 14 ins
We put the shared libraries in base_libdir because at least
one library under base_libdir, pam_cracklib.so, needs them
and will cause a qa warning when it is built.
---
meta/recipes-core/zlib/zlib_1.2.7.bb | 14 ++
1 files changed, 14 insertions(+), 0 deletions(-)
diff --git a/meta/
