All of lore.kernel.org
 help / color / mirror / Atom feed
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 15:55:39 +0100	[thread overview]
Message-ID: <CA+chaQfz1S1H4240eArHGYEc8Dh=ghzyLYVm1Eu8JyBWbgWMvA@mail.gmail.com> (raw)
In-Reply-To: <5116A5DA.90500@topic.nl>

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

use sstate-diff-machines.sh



On Sat, Feb 9, 2013 at 8:39 PM, Mike Looijmans <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>
>>> 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
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
>

[-- Attachment #2: Type: text/html, Size: 2833 bytes --]

  reply	other threads:[~2013-02-10 15:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29  9:29 Multiple MACHINE building is broken in OE-core? Mike Looijmans
2013-01-29  9:40 ` Martin Jansa
2013-01-29 10:21   ` Mike Looijmans
2013-01-29 10:48     ` Burton, Ross
     [not found]       ` <510B73EB.8060907@topic.nl>
     [not found]         ` <CAJTo0LbkOMXqZkHd-JAcNKxiOmXTy+TXPEEJ-CkPc1Jx3Ujekg@mail.gmail.com>
2013-02-01 12:59           ` Mike Looijmans
2013-02-01 14:00             ` Burton, Ross
2013-02-09 19:39             ` Mike Looijmans
2013-02-10 14:55               ` Martin Jansa [this message]
2013-02-10 19:02                 ` Mike Looijmans
2013-02-10 19:59                   ` Martin Jansa
2013-02-18 11:04                     ` OE-core] How do I find out why are packages being rebuilt? Mike Looijmans
2013-02-18 11:11                       ` Burton, Ross
2013-02-18 13:14                         ` Mike Looijmans
2013-02-18 13:19                           ` Burton, Ross
2013-02-18 17:28                           ` Martin Jansa
2013-01-29 11:27     ` Multiple MACHINE building is broken in OE-core? Martin Jansa
2013-02-06  8:02 Cooper Jr., Franklin
2013-02-06  8:56 ` Martin Jansa
2013-02-07 18:00   ` Cooper Jr., Franklin

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='CA+chaQfz1S1H4240eArHGYEc8Dh=ghzyLYVm1Eu8JyBWbgWMvA@mail.gmail.com' \
    --to=martin.jansa@gmail.com \
    --cc=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.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.