Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] zlib: put shared libraries in base_libdir
Date: Wed, 15 May 2013 08:08:18 -0500	[thread overview]
Message-ID: <519388C2.5000706@windriver.com> (raw)
In-Reply-To: <1368611695.6920.79.camel@phil-desktop.brightsign>

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?  From the description it sounds like
> unsafe-references-in-binaries but that one has been disabled since
> 2fb58da56e8e7044de21fd10fe9164d204587236.

We have that enabled in our builds.  We do so because we have customers who 
still want the root, /usr split.

--Mark

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




  reply	other threads:[~2013-05-15 13:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-14 23:35 [PATCH 0/1] zlib: put shared libraries under base_libdir Joe Slater
2013-05-14 23:35 ` [PATCH 1/1] zlib: put shared libraries in base_libdir Joe Slater
2013-05-15  8:47   ` Saul Wold
2013-05-15  9:54   ` Phil Blundell
2013-05-15 13:08     ` Mark Hatle [this message]
2013-05-15 19:50       ` Slater, Joseph
2013-05-15 20:44         ` Phil Blundell
2013-05-15 23:00           ` Slater, Joseph

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=519388C2.5000706@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox