On 07-09-17 11:06, Zoran Stojsavljevic wrote:
> If you keep your sstate-cache directory then delete tmp/ dir is what you need
> to do. Rebuilding from sstate-cache is very quick.
It does not help. Since I'll have at the end/I'll end-up with the same
problem. My best guess. :-(
Since I am building the whole humongous YOCTO build not in one, rather in two
steps, like this:
|bitbake meta-toolchain-qt5 (5 hours build||on my HP EliteBook 840 G1)
||bitbake angstrom-lxde-image| (5 hours build on my HP EliteBook 840 G1)
Here, my best guess is that the first build sets its own hash, which the
second sets also its own (very
different), then makes hash checks in deploy/ tree, and fails... !?
You should be able to do "bitbake meta-toolchain-qt5 angstrom-lxde-image" in
one go. That should be faster than two separate runs.
If you change the DISTRO, you'll invalidate your "tmp" building dir resulting
in loads of new stuff being built.
If you need two distros, make two build enviroments from them. You should
share the sstate-cache directory between them (saves tons on building
compilers and such) but not the "tmp" directory.
On Thu, Sep 7, 2017 at 9:42 AM, Khem Raj <raj.k...@gmail.com
<mailto:raj.k...@gmail.com>> wrote:
On Thu, Sep 7, 2017 at 12:37 AM, Zoran Stojsavljevic
<zoran.stojsavlje...@gmail.com <mailto:zoran.stojsavlje...@gmail.com>>
wrote:
> While re-compiling the whole YOCTO load for freescale i.MX6, where I have
> added Qt5 layers (and it failed many times, so I needed to do some tricks
> there), I encounter the following warning (in ORANGE) and error (in RED)
> while finishing the build:
>
> WARNING: Duplicate inclusion for
>
/home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-bsp-common/conf/tdx_version.conf
> in
>
/home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-demos/recipes-images/images/tdx-image-fstype.inc
> ERROR: When reparsing
>
/home/user/toradex/Qt5-plus-x11/oe-core/build/../layers/meta-toradex-demos/recipes-images/images/angstrom-lxde-image.bb.do_image_teziimg,
> the basehash value changed from b7b4f312b8b657bfdd068ebd8e2dd104 to
> 1e71714a9c01964cdc724c52290abee4. The metadata is not deterministic and
this
> needs to be fixed.
> NOTE: Tasks Summary: Attempted 7415 tasks of which 7394 didn't need to be
> rerun and all succeeded.
> NOTE: Writing buildhistory
>
> It built (after all) complete deploy with all the images. I kind of get
what
> is going on here.
>
> Question: how to rebuild the complete deploy/images NOT deleting tmp/? It
> compiled overall (in two steps) > 10h. Do I need to touch some file?
>
if you keep your sstate-cache directory then delete tmp/ dir is what you
need
to do. Rebuilding from sstate-cache is very quick
> Thank you,
> Zoran
>
>
> --
>
Kind regards,
Mike Looijmans
System Expert
TOPIC Products
Materiaalweg 4, NL-5681 RJ Best
Postbus 440, NL-5680 AK Best
Telefoon: +31 (0) 499 33 69 79
E-mail: mike.looijm...@topicproducts.com
Website: www.topicproducts.com
Please consider the environment before printing this e-mail
_______________________________________________
> yocto mailing list
> yocto@yoctoproject.org <mailto:yocto@yoctoproject.org>
> https://lists.yoctoproject.org/listinfo/yocto
<https://lists.yoctoproject.org/listinfo/yocto>
>
--
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
