[OE-core] Multiple MACHINE building is broken in OE-core?

Mike Looijmans mike.looijmans at topic.nl
Sun Feb 10 19:02:10 UTC 2013

This is as far as I get with that:

milo at phenom:/media/work/pliqt/openpli-oe-core/build/tmp/sstate-diff/1360521554$ bitbake-diffsigs */mips32el-oe-linux/*/*.do_build.sigdata.*Dependency on task aio-grab.bb.do_package_write was added with hash f5d90bf1c666db003dd2d94ee76336f9
Dependency on task aio-grab.bb.do_packagedata was added with hash a38438167f9ca58d98348d57d4e6d21b
Dependency on task aio-grab.bb.do_populate_lic was added with hash 6958863d843c018d99431de6177085e8
Dependency on task aio-grab.bb.do_package was added with hash 8ffde91a0ec162c7c54f3df92e3e7def
Dependency on task aio-grab.bb.do_populate_sysroot was added with hash 5d3321301154d8f6dc6d123c2ce2b6f5
Dependency on task jpeg_8d.bb.do_package_write was added with hash af2231b8098bfdf1ab8669bbc79747fa
Dependency on task zlib_1.2.7.bb.do_package_write was added with hash a927be1c19c94353a60a9e9bf29eae5a
Dependency on task libpng_1.5.13.bb.do_package_write was added with hash bd084eeb607a74436205df614004b920
Dependency on task alsa-lib_1.0.25.bb.do_package was removed with hash b5ab01fbe4eb3705c67ba63f23fb5b08
Dependency on task alsa-lib_1.0.25.bb.do_package_write was removed with hash bc21dd95ffa4579a27e7b23e52a1dc2c
Dependency on task alsa-lib_1.0.25.bb.do_packagedata was removed with hash 4178fd5aecec1780b7a8f885c609978d
Dependency on task alsa-lib_1.0.25.bb.do_populate_sysroot was removed with hash 8f6d124c5c3af523b9c110913121301c
Dependency on task alsa-lib_1.0.25.bb.do_populate_lic was removed with hash b4f78811c2789853f340ff5368982184
milo at phenom:/media/work/pliqt/openpli-oe-core/build/tmp/sstate-diff/1360521554$ bitbake-diffsigs */mips32el-oe-linux/gcc-runtime/4.7.2-r17.do_build.sigdata.*
Hash for dependent task gcc-runtime_4.7.bb.do_package changed from 3d17db8868ffdf887f2c1eafad2913d3 to 6cbeed612f989e2fa242aabf44e8b04d
Hash for dependent task libgcc_4.7.bb.do_package_write changed from 781c412ac431551e84b8e4cfc6e74510 to 5ecb8417095004067b9b7ed90869489a
Hash for dependent task gcc-runtime_4.7.bb.do_package_write changed from cf1b775ba849fad691383b9b34744606 to ed0fc87a27bee8a9824cc6b641e5fa1e
Hash for dependent task gcc-runtime_4.7.bb.do_packagedata changed from 803c9c54763ca265436c601bfe89d414 to 19910ef7091f97ad5bce4dd9861b1506
Hash for dependent task eglibc_2.17.bb.do_package_write changed from 9e3137c59022904d9c93d2425caf2459 to 4342976c1d5fa671793c1ebed92b9b8e
milo at phenom:/media/work/pliqt/openpli-oe-core/build/tmp/sstate-diff/1360521554$

Any tips on interpreting this further?

Met vriendelijke groet / kind regards,

Mike Looijmans

[cid:image6b1258.GIF at 29fbd82e.4da8fd68]

Topic Embedded Systems
Eindhovenseweg 32c      T:      +31 (0)499 33 69 79
5683 KH Best    F:      +31 (0)499 33 69 70
Postbus 440     E:      mike.looijmans at topic.nl
5680 AK Best    W:      www.topic.nl<http://www.topic.nl>


Dit e-mail bericht en de eventueel daarbij behorende bijlagen zijn uitsluitend bestemd voor de geadresseerde, zoals die blijkt uit het e-mail bericht en/of de bijlagen. Er kunnen gegevens met betrekking tot een derde instaan. Indien u als niet-geadresseerde dit bericht en de bijlagen ontvangt, terwijl u niet bevoegd of gemachtigd bent om dit bericht namens de geadresseerde te ontvangen, wordt u verzocht de afzender hierover direct te informeren en het e-mail bericht met de bijlagen te vernietigen. Ieder gebruik van de inhoud van het e-mail bericht, waaronder de daarbij behorende bijlagen, door een ander dan de geadresseerde is onrechtmatig jegens ons dan wel de eventueel in het e-mail bericht of de bijlagen voorkomende andere personen. TOPIC Embedded Systems is niet aansprakelijk voor enigerlei schade voortvloeiend uit het gebruik en/of acceptatie van dit e-mail bericht of de daarbij behorende bijlagen.

The contents of this message, as well as any enclosures, are addressed personally to, and thus solely intended for the addressee. They may contain information regarding a third party. A recipient who is neither the addressee, nor empowered to receive this message on behalf of the addressee, is kindly requested to immediately inform the sender of receipt, and to destroy the message and the enclosures. Any use of the contents of this message and/or the enclosures by any other person than the addressee or person who is empowered to receive this message, is illegal towards the sender and/or the aforementioned third party. TOPIC Embedded Systems is not liable for any damage as a result of the use and/or acceptance of this message and as well as any enclosures.
Van: Martin Jansa [martin.jansa at gmail.com]
Verzonden: zondag 10 februari 2013 15:55
Aan: Mike Looijmans

use sstate-diff-machines.sh

On Sat, Feb 9, 2013 at 8:39 PM, Mike Looijmans <mike.looijmans at topic.nl<mailto:mike.looijmans at topic.nl>> wrote:
On 02/01/2013 01:59 PM, Mike Looijmans wrote:
On 02/01/2013 11:29 AM, Burton, Ross wrote:
On 1 February 2013 07:51, Mike Looijmans <mike.looijmans at topic.nl<mailto:mike.looijmans at topic.nl>> wrote:
A concrete example might help.

Would be glad to comply, if you care to explain what you need. What
should I
do, which logging to collect (and maybe how)?

To start with just the two machines you are changing between and the
packages/tasks that are re-ran.

Well, here's an example of me switching from "vusolo2" to "et9x00" in the current state of OE. I'm migrating this from a year-old or so state of OE-core to the present.

On the "old" system (not "classic" openembedded, just a much older oe-core!) switching would result in just immediately building rootfs, and nothing more.

Now when I change MACHINE from one to the other, after just having built, it runs hundreds of tasks, and it takes a few minutes to do all that.

$ export MACHINE=et9x00
$ bitbake my-image
$ export MACHINE=vusolo2
$ bitbake my-image > /tmp/bitbake.log
$ export MACHINE=et9x00
$ bitbake my-image > /tmp/bitbake.log

I've attached the two log files.

WHY is it doing all that? None of these packages are machine specific!
Mike Looijmans - Topic Automation

Openembedded-core mailing list
Openembedded-core at lists.openembedded.org<mailto:Openembedded-core at lists.openembedded.org>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20130210/8bca2c18/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image6b1258.GIF
Type: image/gif
Size: 5751 bytes
Desc: image6b1258.GIF
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20130210/8bca2c18/attachment-0002.gif>

More information about the Openembedded-core mailing list