From: Gary Thomas <gary@mlbassoc.com>
To: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Lots of errors building SDK
Date: Tue, 26 Jul 2016 13:41:37 +0200 [thread overview]
Message-ID: <57974C71.5080402@mlbassoc.com> (raw)
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
------------------------------------------------------------
reply other threads:[~2016-07-26 11:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=57974C71.5080402@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.