From: Gary Thomas <gary@mlbassoc.com>
To: "Daniel." <danielhilst@gmail.com>, Khem Raj <raj.khem@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: meta-toolchain build errors
Date: Sat, 2 Jul 2016 08:29:14 +0200 [thread overview]
Message-ID: <57775F3A.5030905@mlbassoc.com> (raw)
In-Reply-To: <CAF3SDA6dNkV_=mPYHcymffN-CCDgS4KxdXohfZmyBdoeOyA-LA@mail.gmail.com>
On 2016-07-01 14:21, Daniel. wrote:
> Did you tried "bitbake -fc cleanall imx6-demo-image && bitbake
> imx6-demo-image" !?
I [effectively] did the same - started with an empty/new build and then
% bitbake imx6-demo-image
% bitbake imx6-demo-image -c populate_sdk
Anyone know the innards enough to know what files I can compare to see
where the mismatches are coming from?
>
> 2016-06-30 12:05 GMT-03:00 Khem Raj <raj.khem@gmail.com>:
>>
>>
>> On Thursday, June 30, 2016, Gary Thomas <gary@mlbassoc.com> wrote:
>>>
>>> On 2016-06-29 17:27, Khem Raj wrote:
>>>>
>>>> On Jun 29, 2016 4:10 AM, "Gary Thomas" <gary@mlbassoc.com
>>>> <mailto:gary@mlbassoc.com>> wrote:
>>>> >
>>>> > I just [successfully] built a large image for my target (details):
>>>> > BB_VERSION = "1.31.0"
>>>> > BUILD_SYS = "x86_64-linux"
>>>> > NATIVELSBSTRING = "Ubuntu-15.10"
>>>> > TARGET_SYS = "arm-amltd-linux-gnueabi"
>>>> > MACHINE = "teton-p0382"
>>>> > DISTRO = "amltd"
>>>> > DISTRO_VERSION = "2.1+snapshot-20160629"
>>>> > TUNE_FEATURES = "arm armv7a vfp thumb neon
>>>> callconvention-hard cortexa9"
>>>> > TARGET_FPU = "hard"
>>>> > meta = "master:c6d50b272936b61b98a056ea2e1de5d0f4ef53ce"
>>>> > ... platform specifics removed ...
>>>> >
>>>> > Then I tried 'bitbake meta-toolchain' immediately afterwards, only
>>>> > to be assaulted by a barrage of messages like this:
>>>> >
>>>> > ERROR: nativesdk-libsdl-1.2.15-r3 do_populate_sysroot: Taskhash
>>>> mismatch 8ac6cdc4e26ea7fb43e76f0f9ce3def0 verses
>>>> b05a369a00869fc70fe9ba2cc28e7259 for
>>>>
>>>> virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb.do_populate_sysroot
>>>> > ERROR: Taskhash mismatch 8ac6cdc4e26ea7fb43e76f0f9ce3def0 verses
>>>> b05a369a00869fc70fe9ba2cc28e7259 for
>>>>
>>>> virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-graphics/libsdl/libsdl_1.2.15.bb.do_populate_sysroot
>>>> > ERROR: nativesdk-bash-completion-2.1-r0 do_compile: Taskhash mismatch
>>>> 2e063c5bac7bf922fbff59be5120a62e verses
>>>> 0223876e7a4bc1e57f93a44631b4e4aa for
>>>>
>>>> virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-support/bash-completion/bash-completion_2.1.bb.do_compile
>>>> > ERROR: Taskhash mismatch 2e063c5bac7bf922fbff59be5120a62e verses
>>>> 0223876e7a4bc1e57f93a44631b4e4aa for
>>>>
>>>> virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-support/bash-completion/bash-completion_2.1.bb.do_compile
>>>> > ERROR: nativesdk-bash-completion-2.1-r0 do_install: Taskhash mismatch
>>>> a9932697b29f5fbd06feafedea44d7d4 verses
>>>> 0b4e83ecda4ce5560e50891715d6a5d1 for
>>>>
>>>> virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-support/bash-completion/bash-completion_2.1.bb.do_install
>>>> > ERROR: Taskhash mismatch a9932697b29f5fbd06feafedea44d7d4 verses
>>>> 0b4e83ecda4ce5560e50891715d6a5d1 for
>>>>
>>>> virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-support/bash-completion/bash-completion_2.1.bb.do_install
>>>> > ERROR: nativesdk-bash-completion-2.1-r0 do_package: Taskhash mismatch
>>>> 3cdba66cd643484bed95676b5a4cdc21 verses
>>>> fe3108a63774b61b3910e75495fb4d5d for
>>>>
>>>> virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-support/bash-completion/bash-completion_2.1.bb.do_package
>>>> > ERROR: Taskhash mismatch 3cdba66cd643484bed95676b5a4cdc21 verses
>>>> fe3108a63774b61b3910e75495fb4d5d for
>>>>
>>>> virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-support/bash-completion/bash-completion_2.1.bb.do_package
>>>> > ERROR: nativesdk-qemu-2.6.0-r1 do_configure: Taskhash mismatch
>>>> c8c576da0ae11886e518efa4bc406f18 verses
>>>> ad6e2e5d7704e6002f3b4ec56bc2d92b for
>>>>
>>>> virtual:nativesdk:/local/poky-cutting-edge/meta/recipes-devtools/qemu/qemu_2.6.0.bb.do_configure
>>>> > ...
>>>> > NOTE: Tasks Summary: Attempted 2047 tasks of which 865 didn't need to
>>>> be rerun and all succeeded.
>>>> > Summary: There were 1212 ERROR messages shown, returning a non-zero
>>>> exit code.
>>>> >
>>>> > There were too many error lines to copy :-(
>>>> >
>>>> > What does this mean and how do I get my toolchain?
>>>>
>>>> Bitbake -cpopulate_sdk your-image
>>>
>>>
>>> I tried that and it seems to have worked, but I still got similar error
>>> messages:
>>> ERROR: imx6-demo-image-1.0-r0 do_populate_sdk: Taskhash mismatch
>>> 5313c03c1d0cdd396e6128d6400e41e7 verses 96756bc7f74f66f35df9cb2fe9a596d0 for
>>> /local/poky-cutting-edge/meta-teton-imx6-p0382/packages/images/imx6-demo-image.bb.do_populate_sdk
>>> ERROR: Taskhash mismatch 5313c03c1d0cdd396e6128d6400e41e7 verses
>>> 96756bc7f74f66f35df9cb2fe9a596d0 for
>>> /local/poky-cutting-edge/meta-teton-imx6-p0382/packages/images/imx6-demo-image.bb.do_populate_sdk
>>>
>>> What file(s) can I look at to see why the mismatch happened?
>>>
>>
>> There could be some time related variable coming into checksum. I have seen
>> such errors in other cases. You need to see why signature data contains
>> these variables. One way is delete your tmp and rebuild
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2016-07-02 6:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 11:08 meta-toolchain build errors Gary Thomas
2016-06-29 15:27 ` Khem Raj
2016-06-30 8:06 ` Gary Thomas
2016-06-30 15:05 ` Khem Raj
2016-07-01 12:21 ` Daniel.
2016-07-02 6:29 ` Gary Thomas [this message]
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=57775F3A.5030905@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=danielhilst@gmail.com \
--cc=raj.khem@gmail.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.