Mark Gross reported that trying to build grub on his 64-bit host failed, and the way the error was conveyed was not useful. This bug will track how to improve this error reporting situation.
Note: I've currently got an email inquiry in to Mark to get more details about this issue.
Scott, as discussed earlier I'm looking into this already; at least at the collection end so that we can get access to the reason for the package being skipped. I'm happy to leave the reporting end for you to work on if you'd prefer.
I confirmed with Mark that he would like to see what recipes get skipped due to SkipPackage exceptions: "I blew a bunch of time trying to build qemu64 minimal target before I found that you need the meta-intel layer such that grub 2 would be provided. Recipes-bsp has grub 0.97 but, it raises a SkipPackage exception if the target is not 32 bit." "bitbake -DDD grub would report NoProvider: grub Yet show the grub_0.97.bb was indeed getting processed."
Moving this to M3 because I see little chance of me fixing this *and* bug #542 in this milestone. Richard agreed that bug #542 was the more important one to fix for now.
So we now print out the reason a package has been skipped if a NoProvider error occurs. Is this enough to mark this as fixed?
I think the various changes mean this one is resolved now.