From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by mail.openembedded.org (Postfix) with ESMTP id 3BE876B7CF for ; Thu, 15 Aug 2013 10:14:56 +0000 (UTC) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail.windriver.com (8.14.5/8.14.3) with ESMTP id r7FAEu6I003454 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 15 Aug 2013 03:14:56 -0700 (PDT) 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; Thu, 15 Aug 2013 03:14:56 -0700 Message-ID: <520CAA18.1080706@windriver.com> Date: Thu, 15 Aug 2013 18:14:48 +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: Paul Eggleton References: <520C9F8A.7080703@windriver.com> <2523779.jWvvpX7hhR@helios> In-Reply-To: <2523779.jWvvpX7hhR@helios> Cc: openembedded-core@lists.openembedded.org 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: Thu, 15 Aug 2013 10:14:56 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 08/15/2013 05:44 PM, Paul Eggleton wrote: > Hi Wenzong, > > On Thursday 15 August 2013 17:29:46 wenzong fan wrote: >> 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; > > (See Ross's reply for a pointer to the new test-dependencies script) That would be a good start point, I have run that script once, but looks not any failure occurs. I'll find a box and run it periodically. Thanks Wenzong > >> 2) Run 'configure --help' on each package to spot all of the optional >> dependencies, and convert them into PACKAGECONFIG specs/or any other >> prompts. > > Actually I have started along this line as well, putting the output of > configure --help into buildhistory so you can see the differences. I'm not > totally sure how useful it is at the moment and it will need some smooting out > to avoid known differences (paths etc.). > > Cheers, > Paul >