From: Martin Jansa <martin.jansa@gmail.com>
To: wenzong fan <wenzong.fan@windriver.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: About PACKAGECONFIG audit
Date: Thu, 15 Aug 2013 12:34:22 +0200 [thread overview]
Message-ID: <20130815103422.GB17945@jama> (raw)
In-Reply-To: <520CAA18.1080706@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 1353 bytes --]
On Thu, Aug 15, 2013 at 06:14:48PM +0800, wenzong fan wrote:
> 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 don't believe it, see "State of bitbake world" thread where I've sent
results from last 3 executions.
There is plenty of issues for everybody :)
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]
next prev parent reply other threads:[~2013-08-15 10:33 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 [this message]
2013-08-19 20:46 ` Randy MacLeod
2013-08-20 5:36 ` wenzong fan
2013-08-22 5:53 ` Randy MacLeod
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=20130815103422.GB17945@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--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