Re: [PATCH] cracklib, zlib: install to /lib instead of /usr/libxx

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 15:29:15 -0400	[thread overview]
Message-ID: <50216C8B.20802@windriver.com> (raw)
In-Reply-To: <1344365134.4874.23.camel@x121e.pbcl.net>

On 12-08-07 02:45 PM, Phil Blundell wrote:
> On Tue, 2012-08-07 at 14:43 -0400, Yao Zhao wrote:
>> 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?
> Conventionally, yeah.  I think the linker does search both but the
> development files would traditionally go in /usr/lib.
If don't install libz.a to the same directory, will linker find libz.a 
not libz.so if -L /usr/lib -L /lib?

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