From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail7.windriver.com (mail7.windriver.com [128.224.252.3]) by mail.openembedded.org (Postfix) with ESMTP id 8E92069686 for ; Tue, 20 Aug 2013 05:36:47 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail7.windriver.com (8.14.5/8.14.3) with ESMTP id r7K5aliw003994 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 20 Aug 2013 01:36:48 -0400 (EDT) Received: from [128.224.162.218] (128.224.162.218) by ALA-HCA.corp.ad.wrs.com (147.11.189.40) with Microsoft SMTP Server id 14.2.342.3; Mon, 19 Aug 2013 22:36:46 -0700 Message-ID: <5213006A.5050602@windriver.com> Date: Tue, 20 Aug 2013 13:36:42 +0800 From: wenzong fan User-Agent: Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130623 Thunderbird/17.0.7 MIME-Version: 1.0 To: Randy MacLeod References: <520C9F8A.7080703@windriver.com> <52128427.3020009@windriver.com> In-Reply-To: <52128427.3020009@windriver.com> Cc: 'Patches and discussions about the oe-core layer' Subject: Re: About PACKAGECONFIG audit X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Aug 2013 05:36:47 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 08/20/2013 04:46 AM, Randy MacLeod wrote: > Add Joe Slater who owns US17463: PACKAGECONFIG clean-up. > > > On 13-08-15 05:29 AM, wenzong fan wrote: >> Hi All, >> >> We have seen some problems like this: >> >> $ bitbake libcap >> >> ld: warning: libaudit.so.1, needed by .../lib64/libpam.so, not found >> .../lib64/libpam.so: undefined reference to `audit_open' >> .../lib64/libpam.so: undefined reference to `audit_close' >> ...... >> >> The libaudit has been available and libpam build with it, after we run >> another build with sstate-cache and w/o libaudit, the error occurs. The >> solution in these cases is to use PACKAGECONFIG to lay out dependencies >> on optional packages and make them explicit. We need to run an audit and >> catch all of these issues. >> >> A probable ways maybe: >> >> 1) Run world build to generate the sysroots as much as possible; >> 2) Run 'configure --help' on each package to spot all of the optional >> dependencies, and convert them into PACKAGECONFIG specs/or any other >> prompts. > > We should try to automate or codify this step so that the output is > a list of oe-core package names. > >> 3) Run #1, #2 as an audit script periodically. >> >> Or could we run this check as part of a QA build step? > > Do you mean: > scripts/test-dependencies.sh No, I mean some check steps that if PACKAGECONFIG should be used, not limit to the script. Thanks Wenzong > > // Randy > >> >> >> Thanks >> Wenzong > >