On 2015-05-05 09:21, Paul Eggleton wrote:
Hi Gary,

On Tuesday 05 May 2015 08:44:47 Gary Thomas wrote:
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/packageg
roups /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?

The confusion here is between runtime targets (package names, i.e. what you
should specify in MACHINE_EXTRA_RRECOMMENDS) and build-time targets e.g.
virtual/bootloader. virtual/bootloader is not a runtime target (hence "Nothing
RPROVIDES ..." and thus doesn't belong in MACHINE_EXTRA_RRECOMMENDS. I suspect
what you want instead is:

EXTRA_IMAGEDEPENDS += "virtual/bootloader"

Thanks for the explanation, that fixes my problem.

--
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to