From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.windriver.com ([147.11.1.11]) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1SxNxq-0006D9-3o for openembedded-core@lists.openembedded.org; Fri, 03 Aug 2012 21:55:14 +0200 Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail.windriver.com (8.14.5/8.14.3) with ESMTP id q73JhVDC011155 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Fri, 3 Aug 2012 12:43:31 -0700 (PDT) Received: from [128.224.147.210] (128.224.147.210) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server (TLS) id 14.2.309.2; Fri, 3 Aug 2012 12:43:31 -0700 Message-ID: <501C29D8.7080300@windriver.com> Date: Fri, 3 Aug 2012 15:43:20 -0400 From: Yao Zhao User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: References: <501BFFD9.6060108@windriver.com> <501C0E2C.50108@windriver.com> <501C1369.2030508@windriver.com> <501C16D9.4010502@windriver.com> In-Reply-To: <501C16D9.4010502@windriver.com> X-Originating-IP: [128.224.147.210] Subject: Re: how to fix WARNING: QA Issue: libpam: installed in the base_prefix, requires a shared library under exec_prefix X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list Reply-To: Patches and discussions about the oe-core layer List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Aug 2012 19:55:14 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 12-08-03 02:22 PM, Mark Hatle wrote: > On 8/3/12 1:07 PM, Yao Zhao wrote: >> On 12-08-03 01:45 PM, Mark Hatle wrote: >>> 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. >>> >> libcrack is depending on libz and libz is in usr/lib too. >> Seems libz didn't depend another. >> >> What exactly reason that this is a serious problem? Is this a standard? >> It is quite possible that a lib library depending on usr/lib then ..... >> Do we have a one-shot cure? > > The QA message is because the / (non-/usr) was originally designed to > be the minimal boot environment, and then /usr would be added to > provide the full system capabilities. There are some advantages to > this behavior for embedded systems, as it can allow for smaller > footprint systems to be the boot environment. > > With modern components like udev, systemd, and such, sometimes it's > difficult, if not nearly impossible to have this split though, as many > of the components require libraries and/or binaries that normally > reside in /usr. Generally we have the choice to either move the > libraries or binaries, or break the dependency on those items (by > changing the configuration, statically linking, or changing the > behavior so the library/binary is no longer needed.) > > I suspect libz is needed because the cracklib dictionary is > compressed. Dependending on usage, it may make sense to statically > link libz into libcrack, and move libcrack to /lib. > thanks Mark! I have modified zlib and cracklib both to install to /lib. In case there are other packages installed to /lib but need libz too. patch soon. yao > --Mark > >> yao >>> 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 >>>> >>> >>> >>> _______________________________________________ >>> Openembedded-core mailing list >>> Openembedded-core@lists.openembedded.org >>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core >> >> >> >> _______________________________________________ >> Openembedded-core mailing list >> Openembedded-core@lists.openembedded.org >> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core >> > > > _______________________________________________ > Openembedded-core mailing list > Openembedded-core@lists.openembedded.org > http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core