Op 30 jun 2011, om 13:17 heeft Phil Blundell het volgende geschreven: > On Wed, 2011-06-29 at 14:49 +0100, Richard Purdie wrote: >> On Wed, 2011-06-29 at 14:36 +0100, Phil Blundell wrote: >>> On Tue, 2011-06-28 at 22:32 +0200, Koen Kooi wrote: >>>> From >>>> http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/testlab/commit/?h=yocto&id=0d0e14cda2ddd881d09798b0e6edd8086aa9b6d9 >>>> >>>> +libc6 -> libc6_dev; >>>> >>>> So libc6 now depends on libc6-dev :( >>> >>> I guess it would be straightforward to patch insane.bbclass to detect >>> that particular failure (which does indeed seem to happen to libc >>> distressingly often). It already diagnoses the case where a package >>> erroneously depends on a -dbg package, and I can't think of any reason >>> why the same logic couldn't be applied to -dev. >> >> I'd love to see a patch for this! :) > > Your wish, naturally, is my command. I've built micro-base-image with > this and verified that I didn't get any false positives; I also checked > (via some manual fiddling) that it did indeed detect the case that we > want it to. > > I guess it might be a good idea for someone to test it with a slightly > larger dataset before actually checking it in, just in case.
Does it whitelist recipes that inherit task.bbclass? I have tasks used for beagleboard workshops that drag in the native toolchain and headers for the things we need to build against (e.g. opencv, qt). regards, Koen _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
