Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Yao Zhao <yao.zhao@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] cracklib, zlib: install to /lib instead of /usr/libxx
Date: Tue, 7 Aug 2012 14:43:40 -0400	[thread overview]
Message-ID: <502161DC.9020705@windriver.com> (raw)
In-Reply-To: <1344364696.4874.19.camel@x121e.pbcl.net>

On 12-08-07 02:38 PM, Phil Blundell wrote:
> On Tue, 2012-08-07 at 14:35 -0400, Yao Zhao wrote:
>> On 12-08-07 02:30 PM, Phil Blundell wrote:
>>> Where do libz.a and libz.so end up after your patch?
>> ├── zlib-dev
>> │ ├── lib
>> │ │ └── libz.so -> libz.so.1.2.7
>> └── zlib-staticdev
>> └── lib
>> └── libz.a
> I found the output from "tree" a bit hard to read, but that doesn't look
> right to me.
any reason? It shouldn't go to lib, but still /usr/libxx?

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





  reply	other threads:[~2012-08-07 18:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07 17:31 [PATCH] cracklib, zlib: install to /lib instead of /usr/libxx Yao Zhao
2012-08-07 17:39 ` Derek Buitenhuis
2012-08-07 18:30   ` Yao Zhao
2012-08-07 18:30     ` Phil Blundell
2012-08-07 18:35       ` Yao Zhao
2012-08-07 18:38         ` Phil Blundell
2012-08-07 18:43           ` Yao Zhao [this message]
2012-08-07 18:45             ` Phil Blundell
2012-08-07 19:29               ` Yao Zhao
2012-08-07 21:20                 ` Phil Blundell
2012-08-08 13:24                   ` Yao Zhao
2012-08-08 13:25                     ` Phil Blundell
2012-08-08 13:36                       ` Yao Zhao
2012-08-07 18:35     ` Derek Buitenhuis
2012-08-08 13:26       ` Yao Zhao
2012-08-07 18:17 ` Koen Kooi

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=502161DC.9020705@windriver.com \
    --to=yao.zhao@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