From: Randy MacLeod <randy.macleod@windriver.com>
To: wenzong fan <wenzong.fan@windriver.com>
Cc: 'Patches and discussions about the oe-core layer'
<openembedded-core@lists.openembedded.org>
Subject: Re: About PACKAGECONFIG audit
Date: Thu, 22 Aug 2013 01:53:43 -0400 [thread overview]
Message-ID: <5215A767.3040601@windriver.com> (raw)
In-Reply-To: <5213006A.5050602@windriver.com>
On 13-08-20 01:36 AM, wenzong fan wrote:
> 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.
thread replace by discussion on:
[Bug 5033] New: Way to audit all optional dependencies
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5033
// Randy
>
> Thanks
> Wenzong
>
>>
>> // Randy
>>
>>>
>>>
>>> Thanks
>>> Wenzong
>>
>>
--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350
prev parent reply other threads:[~2013-08-22 5:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 9:29 About PACKAGECONFIG audit wenzong fan
2013-08-15 9:38 ` Burton, Ross
2013-08-15 9:43 ` Phil Blundell
2013-08-15 10:22 ` Martin Jansa
2013-08-16 10:41 ` Richard Purdie
2013-08-16 10:51 ` Phil Blundell
2013-08-15 9:44 ` Paul Eggleton
2013-08-15 10:14 ` wenzong fan
2013-08-15 10:34 ` Martin Jansa
2013-08-19 20:46 ` Randy MacLeod
2013-08-20 5:36 ` wenzong fan
2013-08-22 5:53 ` Randy MacLeod [this message]
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=5215A767.3040601@windriver.com \
--to=randy.macleod@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wenzong.fan@windriver.com \
/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