From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Lu, Lianhao" <lianhao.lu@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: Determining dependencies by looking under work or tmp?
Date: Tue, 24 Apr 2012 10:11:42 +0100 [thread overview]
Message-ID: <1335258702.12692.113.camel@ted> (raw)
In-Reply-To: <857BE142E5399E46B20FD45B9DB8A7BC0FD71ED9@SHSMSX101.ccr.corp.intel.com>
On Tue, 2012-04-24 at 01:55 +0000, Lu, Lianhao wrote:
> Peter Tornel wrote on 2012-04-24:
> > Hello Group,
> >
> > I'm wondering why some packages were built in my work directory even though I didn't specify them in my recipes and they didn't show up
> > in my rootfs. For example, I find strace under work, but I don't find it in my rootfs. There are some others I'm wondering about too.
> >
> > Is there evidence left in work or somewhere under tmp for a particular package that shows why it was built or what dependency it filled?
>
> Please try "bitbake -g"
Also, "bitbake -g -u depexp" can provide some insight to some of these
kinds of questions.
Cheers,
Richard
prev parent reply other threads:[~2012-04-24 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 1:19 Determining dependencies by looking under work or tmp? Peter Tornel
2012-04-24 1:55 ` Lu, Lianhao
2012-04-24 9:11 ` Richard Purdie [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=1335258702.12692.113.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=lianhao.lu@intel.com \
--cc=poky@yoctoproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.