Thank you so much for having a crack at this. Your results have allowed me to dig a bit deeper into this issue.
I'm still trying to narrow down the exact issue but here's what I have so far. I'm working with the git repository, but I've been playing around with this for about a week, so I'm not 100% up to date. Specifically I'm using: master:c206007235df3e00c21a1cbf30e8a1bccc07a9e5 Starting with that repository I follow the regular steps: $ poky/oe-init-build qemux86 then I edit the conf/local.conf to end up with the following (virtually no changes, just the lines at the end): PARALLEL_MAKE = "-j 8" MACHINE ??= "qemux86" DISTRO ?= "poky" PACKAGE_CLASSES ?= "package_rpm" EXTRA_IMAGE_FEATURES = "debug-tweaks" USER_CLASSES ?= "buildstats image-mklibs image-prelink" PATCHRESOLVE = "noop" CONF_VERSION = "1" BB_DANGLINGAPPENDS_WARNONLY = "yes" PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt" then I perform $ bitbake core-image-minimal everything goes well. I then add the following line to the end of my conf/local.conf IMAGE_INSTALL_append = " trace-cmd" and run $ bitbake core-image-minimal everything builds just fine. Then I modify that last line as follows: IMAGE_INSTALL_append = " trace-cmd bash" now when I try to build I get: Build Configuration: BB_VERSION = "1.16.0" TARGET_ARCH = "i586" TARGET_OS = "linux" MACHINE = "qemux86" DISTRO = "poky" DISTRO_VERSION = "1.3+snapshot-20121126" TUNE_FEATURES = "m32 i586" TARGET_FPU = "" meta meta-yocto meta-yocto-bsp = "master:c206007235df3e00c21a1cbf30e8a1bccc07a9e5" NOTE: Resolving any missing task queue dependencies NOTE: Preparing runqueue NOTE: Executing SetScene Tasks NOTE: Executing RunQueue Tasks ERROR: Function failed: do_rootfs (see /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.19668 for further information) ERROR: Logfile of failure stored in: /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.19668 Log data follows: | DEBUG: Executing shell function do_rootfs | Generating solve db for /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/deploy/rpm/qemux86... | Generating solve db for /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/deploy/rpm/i586... | Generating solve db for /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/deploy/rpm/all... | total: 1 0.000000 MB 2.930406 secs | fingerprint: 1104 0.032554 MB 0.063469 secs | install: 368 0.000000 MB 0.878790 secs | digest: 736 5.357010 MB 0.027508 secs | signature: 736 0.000000 MB 1.443277 secs | dbadd: 368 0.000000 MB 0.866237 secs | dbget: 12620 0.000000 MB 0.018020 secs | dbput: 368 3.063072 MB 0.541058 secs | readhdr: 3681 6.087218 MB 0.010347 secs | hdrload: 1929 10.076294 MB 0.012106 secs | hdrget: 70812 0.000000 MB 0.081749 secs | Generating solve db for /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/deploy/rpm/all... | Processing packagegroup-core-boot... | Processing trace-cmd... | Processing bash... | Unable to resolve package bash | ERROR: some packages were missing | ERROR: Function failed: do_rootfs (see /home/trevor/devel/yocto/gitrepo-method/qemux86/tmp/work/qemux86-poky-linux/core-image-minimal/1.0-r0/temp/log.do_rootfs.19668 for further information) ERROR: Task 7 (/home/trevor/devel/yocto/gitrepo-method/poky/meta/recipes-core/images/ core-image-minimal.bb, do_rootfs) failed with exit code '1' NOTE: Tasks Summary: Attempted 1443 tasks of which 1442 didn't need to be rerun and 1 failed. No currently running tasks (1442 of 1444) Summary: 1 task failed: /home/trevor/devel/yocto/gitrepo-method/poky/meta/recipes-core/images/ core-image-minimal.bb, do_rootfs Summary: There was 1 ERROR message shown, returning a non-zero exit code. Can anyone reproduce this? It doesn't make sense. Initially when I first saw this problem, I had been using building "core-image-rt" so I thought it had something to do with that image. But my tests from today seem to indicate that it doesn't since I was able to reproduce my problem with "core-image-minimal" too. I haven't yet figured out if the "PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"" line might be the culprit.
_______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
