From: Gary Thomas <gary@mlbassoc.com>
To: Poky <poky@lists.pokylinux.org>
Subject: How can a package I didn't ask for get included in my image?
Date: Tue, 06 Mar 2012 10:05:47 -0700 [thread overview]
Message-ID: <4F5643EB.70909@mlbassoc.com> (raw)
Note: I'm not sure the best list to use for this, but I'll start
here. I build using poky plus my own distro.conf and my own image
recipes, etc. My example below uses stylized package and target
names.
I'm trying to figure out why a particular package is ending up
in my final image. If I build something like this:
% bitbake my-image
If I then look, I find packages that were installed that I'm
never mentioning:
% grep firmware tmp/work/my-board/my-image/temp/log.do_rootfs
Installing linux-firmware-wl12xx (0.0+git1+09c949f6d3196a7199eb2c7015bfa5d34ed723b5-r0) to root...
so I tried to figure out how this is getting in
% bitbake my-image -g
% grep firmware *.dot
... comes up empty
To be fair, I had originally built this image with this in <my-board>.conf
MACHINE_EXTRA_RRECOMMENDS = " kernel-modules linux-firmware-wl12xx "
but that has since been removed. Somehow, it's ghost lingers on...
How can this be?
How can I get rid of it, short of a complete rebuild?
Thanks for any insight into this mystery.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2012-03-06 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-06 17:05 Gary Thomas [this message]
2012-03-06 17:39 ` How can a package I didn't ask for get included in my image? Gary Thomas
2012-03-06 19:26 ` Paul Eggleton
2012-03-06 20:15 ` Foinel
2012-03-06 21:50 ` Khem Raj
2012-03-06 22:38 ` Paul Eggleton
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=4F5643EB.70909@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@lists.pokylinux.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.