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

[Mike Looijmans]

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> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bitbake-switch-from-et9x00-to-vusolo2.log
Type: text/x-log
Size: 300546 bytes
Desc: not available
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20130209/f25aea04/attachment-0004.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bitbake-switch-from-vusolo2-to-et9x00.log
Type: text/x-log
Size: 268927 bytes
Desc: not available
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20130209/f25aea04/attachment-0005.bin>