From: Gary Thomas <gary@mlbassoc.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Confusing error
Date: Tue, 05 May 2015 08:44:47 -0600 [thread overview]
Message-ID: <5548D75F.3040102@mlbassoc.com> (raw)
I'm getting a very confusing error from bitbake. I'm using a snapshot
from Poky/Yocto (equivalent to 1.8 release) with my own $DISTRO
$ bitbake nand-installer-image
NOTE: Started PRServer with DBfile: /home/gary/tmp/p0381_2015-05-05/p0381_build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 41585, PID: 460
Loading cache: 100% |###################################################################################| ETA: 00:00:00
Loaded 1708 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
ERROR: Nothing RPROVIDES 'virtual/bootloader' (but /home/gary/tmp/p0381_2015-05-05/opt/amltd/poky/meta-amltd/packages/packagegroups /packagegroup-amltd.bb RDEPENDS on or
otherwise requires it)
NOTE: Runtime target 'virtual/bootloader' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['virtual/bootloader']
NOTE: Runtime target 'packagegroup-amltd-boot' is unbuildable, removing...
Missing or unbuildable dependency chain was: ['packagegroup-amltd-boot', 'virtual/bootloader']
ERROR: Required build target 'nand-installer-image' has no buildable providers.
Missing or unbuildable dependency chain was: ['nand-installer-image', 'packagegroup-amltd-boot', 'virtual/bootloader']
But, there is such a provider and I can build it (from the same build tree):
$ bitbake virtual/bootloader
NOTE: Started PRServer with DBfile: /home/gary/tmp/p0381_2015-05-05/p0381_build/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 43428, PID: 515
Loading cache: 100% |###################################################################################| ETA: 00:00:00
Loaded 1708 entries from dependency cache.
NOTE: Resolving any missing task queue dependencies
Build Configuration:
BB_VERSION = "1.27.0"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING = "Fedora-17"
TARGET_SYS = "arm-amltd-linux-gnueabi"
MACHINE = "teton-p0381"
DISTRO = "amltd"
DISTRO_VERSION = "1.8+snapshot-2015-05-05"
TUNE_FEATURES = "arm armv7a vfp neon callconvention-hard cortexa7"
TARGET_FPU = "vfp-neon"
meta
meta-oe
meta-amltd
meta-teton-ls1-p0381
meta-fsl-arm
meta-fsl-arm-extra
meta-browser = "<unknown>:<unknown>"
NOTE: Preparing RunQueue
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
...
After much research, I found that this is happening because I have
MACHINE_EXTRA_RRECOMMENDS="virtual/bootloader linux-firmware-iwlwifi-5xxx"
If I remove the 'virtual/bootloader' from MACHINE_EXTRA_RRECOMMENDS,
the confusion (and error) go away. Any ideas what's happening and why
I might be getting this confusing error?
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next reply other threads:[~2015-05-05 14:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 14:44 Gary Thomas [this message]
2015-05-05 15:21 ` Confusing error Paul Eggleton
2015-05-05 15:58 ` Gary Thomas
-- strict thread matches above, loose matches on Subject: below --
2017-01-12 10:19 Gary Thomas
2017-01-12 10:25 ` Gary Thomas
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=5548D75F.3040102@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@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.