Skip to contentSkip to conversation

Stale warning?

DISCUSSION Gary Thomas 2 participants 2 messages Aug 4, 2015 – Aug 5, 2015

lore
Share & tools
lore
#0 lore raw

While I was fixing the python3 nativesdk recipe, I ran this step a few times:

  $ bitbake nativesdk-python3 -C compile

After this, I get this warning:
WARNING: virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-devtools/python/python3_3.4.3.bb.do_compile is tainted from a forced run
which seems quite reasonable. Once I had the compile errors
fixed, I moved the patches into the recipe and then rebuilt
from scratch (just the nativesdk-python3). Even though the
package has been completely rebuilt (fetch/patch/...), I still
get this warning, which doesn't seem right to me. The warning
only goes away if I clean the package:

  $ bitbake nativesdk-python3 -c clean
Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw

Hi Gary,

Quoted 14 lines · On Tuesday 04 August 2015 09:04:59 Gary Thomas wrote:

While I was fixing the python3 nativesdk recipe, I ran this step a few times:

   $ bitbake nativesdk-python3 -C compile

After this, I get this warning:
WARNING:
virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-devtools/python/pyt hon3_3.4.3.bb.do_compile is tainted from a forced run which seems quite reasonable. Once I had the compile errors
fixed, I moved the patches into the recipe and then rebuilt from scratch (just the nativesdk-python3). Even though the package has been completely rebuilt (fetch/patch/...), I still get this warning, which doesn't seem right to me. The warning only goes away if I clean the package:

Quoted 1 line
   $ bitbake nativesdk-python3 -c clean

This is by design, although I would agree that it would be better if it were able to tell if it could reasonably remove the taint on a rebuild and do so automatically. Since this is something that's come up before (and I've lamented myself) I've filed an enhancement request so we have it tracked:

https://bugzilla.yoctoproject.org/show_bug.cgi?id=8100

At the moment it's marked "future" as I can't make any commitment to implementing it any time soon - someone else is welcome to have a go though.

Cheers,
Paul

Signature · 2 lines
Paul Eggleton
Intel Open Source Technology Centre