Re: Multiple MACHINE building is broken in OE-core?

From: Martin Jansa <martin.jansa@gmail.com>
To: Mike Looijmans <mike.looijmans@topic.nl>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Multiple MACHINE building is broken in OE-core?
Date: Sun, 10 Feb 2013 20:59:19 +0100	[thread overview]
Message-ID: <20130210195919.GA3300@jama> (raw)
In-Reply-To: <A551BDF323A45B48ACE6A404AA16A1C4127A434C@TOP-EX01.TOPIC.LOCAL>

[-- Attachment #1: Type: text/plain, Size: 2666 bytes --]

On Sun, Feb 10, 2013 at 07:02:10PM +0000, Mike Looijmans wrote:
> This is as far as I get with that:
> 
> milo@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
> milo@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.*
> milo@phenom:/media/work/pliqt/openpli-oe-core/build/tmp/sstate-diff/1360521554$
> 
> Any tips on interpreting this further?

comparing do_build is not so useful, compare those do_package

> ________________________________
> Van: Martin Jansa [martin.jansa@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@topic.nl<mailto:mike.looijmans@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@topic.nl<mailto:mike.looijmans@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@lists.openembedded.org<mailto:Openembedded-core@lists.openembedded.org>
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> 
> 


-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]