public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Mike Looijmans <mike.looijmans@topic.nl>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Multiple MACHINE building is broken in OE-core?
Date: Fri, 01 Feb 2013 13:59:41 +0100	[thread overview]
Message-ID: <510BBC3D.1030207@topic.nl> (raw)
In-Reply-To: <CAJTo0LbkOMXqZkHd-JAcNKxiOmXTy+TXPEEJ-CkPc1Jx3Ujekg@mail.gmail.com>

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.

How can I get a list of packages/tasks? They just flash by on screen, 
but I bet there's a convenient flag that I can pass to bitbake to get 
what I want.

One case was between "zynq-zc702" and "zedboard" using my BSP overlay on 
https://github.com/milosoftware/meta-zynq
Both boards have the same SOC, just different board configurations.

Another is when switching from settop box "et9x00" to "vusolo2" in the 
upcoming OpenPLi at 
http://openpli.git.sourceforge.net/git/gitweb.cgi?p=openpli/openpli-oe-core;a=shortlog;h=refs/heads/upstream
The latter failed so miserably that I had to remove the whole "tmp" 
directory and start over to get it to build at all for either of them.


 > As Martin said, switching machine
> will mean a new sysroot so you'll see lots of setscene tasks running
> for every package to start with, but that will only take a minute.

Would using INHERIT += "rm_work" in my config files be problematic here? 
If I need to preserve all the work items, I'll go and buy a bigger 
harddisk, but it's more efficient to just clean up.

Mike.

(sorry, forgot to click the "reply to list" button in my previous response)



  parent reply	other threads:[~2013-02-01 13:15 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 [this message]
2013-02-01 14:00             ` Burton, Ross
2013-02-09 19:39             ` Mike Looijmans
2013-02-10 14:55               ` Martin Jansa
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
  -- strict thread matches above, loose matches on Subject: below --
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=510BBC3D.1030207@topic.nl \
    --to=mike.looijmans@topic.nl \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox