Lots of errors building SDK

Lots of errors building SDK

[Gary Thomas]

I had a working image which I have built & rebuilt over the
last few weeks.  I have no errors or warnings when building
my main image.

Today I wanted to build an SDK for my image, so I ran:
   % bitbake production-testing-image -c populate_sdk    (my own image)
This yielded tons of errors like:
   ERROR: nativesdk-glibc-initial-2.24-r0 do_patch: Taskhash mismatch 0a527f90fe824c09fd0af5628b09721f verses 
2df1210df0097c4f54716ba1a706679c for 
virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-core/glibc/glibc-initial_2.24.bb.do_patch
   ERROR: Taskhash mismatch 0a527f90fe824c09fd0af5628b09721f verses 2df1210df0097c4f54716ba1a706679c for 
virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-core/glibc/glibc-initial_2.24.bb.do_patch
   ERROR: nativesdk-glibc-2.24-r0 do_patch: Taskhash mismatch ba9c1a6d1fafff0e80adc20185f4d6ad verses 
84c5b9feffbf7a6b04e85d29b4a342a5 for 
virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-core/glibc/glibc_2.24.bb.do_patch
   ERROR: Taskhash mismatch ba9c1a6d1fafff0e80adc20185f4d6ad verses 84c5b9feffbf7a6b04e85d29b4a342a5 for 
virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-core/glibc/glibc_2.24.bb.do_patch
   ERROR: nativesdk-linux-libc-headers-4.4-r0 do_configure: Taskhash mismatch 93c93e75b86669d736b9ef9001170e31 verses 
2179a9d0b1b9a52427aacd26b7d9f128 for 
virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.4.bb.do_configure
   ERROR: Taskhash mismatch 93c93e75b86669d736b9ef9001170e31 verses 2179a9d0b1b9a52427aacd26b7d9f128 for 
virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.4.bb.do_configure
   ERROR: nativesdk-linux-libc-headers-4.4-r0 do_compile: Taskhash mismatch ad40492457ea4f72cf5d7d4dbed2fecf verses 
17eaa3e604299fcdee7786829e329d48 for 
virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-kernel/linux-libc-headers/linux-libc-headers_4.4.bb.do_compile
   ...

The build proceeds, but the "ERROR" lines are bothersome.
What can I do to understand why this happened and should I
worry about the result if it succeeds?

n.b. I'm doing this to help mitigate issues with customers
that don't/can't have a native python3 > 3.4.+ on their
build hosts.  Maybe there is another solution?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------