* Stuck tainted task
@ 2016-07-20 6:50 Gary Thomas
0 siblings, 0 replies; only message in thread
From: Gary Thomas @ 2016-07-20 6:50 UTC (permalink / raw)
To: yocto@yoctoproject.org
Sometimes I like to make a quick change/test, e.g. in the Linux
kernel, and then rebuild using
% bitbake virtual/kernel -C compile
This works great and does just what I want. However, the "tainted
task" flag remains even if the recipe is rebuilt from scratch, say
after I commit the change and update my kernel recipe. Shouldn't
it be cleared if some task (step/phase) which precedes it is run?
To be clear, this message happens every run after the "-C compile" run:
WARNING: /local/poky-cutting-edge/meta-fsl-arm-extra/recipes-kernel/linux/linux-boundary_3.14.52.bb.do_compile is
tainted from a forced run
and the only way to clear it is to run
% bitbake virtual/kernel -c clean
Is this behavior correct, or buggy?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-07-20 6:50 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-07-20 6:50 Stuck tainted task Gary Thomas
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.