All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: how to fix WARNING: QA Issue: libpam: installed in the base_prefix, requires a shared library under exec_prefix
Date: Fri, 3 Aug 2012 12:45:16 -0500	[thread overview]
Message-ID: <501C0E2C.50108@windriver.com> (raw)
In-Reply-To: <501BFFD9.6060108@windriver.com>

On 8/3/12 11:44 AM, Yao Zhao wrote:
> Hi all,
>
> Any suggestion to fix these kinds of QA warnings?
>
> libpam is referencing /usr/lib/libcrack from /lib/security.
>
> I tried to fix cracklib to install to /lib but cracklib is using other
> libraries from /usr/lib, I am afraid that I am touching a chain, so any
> good ideas?

Historically I'm used to cracklib being in /lib... but I also don't remember a 
huge chain of additional libraries.

It may be worth identifying the chain and seeing if we can break it, or at least 
reduce it in some fairly easy way.

--Mark

> thanks,
> yao
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>




  reply	other threads:[~2012-08-03 17:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 16:44 how to fix WARNING: QA Issue: libpam: installed in the base_prefix, requires a shared library under exec_prefix Yao Zhao
2012-08-03 17:45 ` Mark Hatle [this message]
2012-08-03 18:07   ` Yao Zhao
2012-08-03 18:22     ` Mark Hatle
2012-08-03 19:43       ` 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=501C0E2C.50108@windriver.com \
    --to=mark.hatle@windriver.com \
    --cc=openembedded-core@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 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.