public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: "Cooper Jr., Franklin" <fcooper@ti.com>
Cc: "Openembedded-core@lists.openembedded.org"
	<Openembedded-core@lists.openembedded.org>
Subject: Re: Multiple MACHINE building is broken in OE-core?
Date: Wed, 6 Feb 2013 09:56:44 +0100	[thread overview]
Message-ID: <20130206085644.GR3271@jama> (raw)
In-Reply-To: <8F29D6B095ED194EA1980491A5E029710C38764C@DFLE09.ent.ti.com>

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

On Wed, Feb 06, 2013 at 08:02:31AM +0000, Cooper Jr., Franklin wrote:
> Hi Everyone,
> 
> While performing denzil to danny work I ran into this same issue that Mike mentioned. I have 4 machines that are armv7a based and previously in denzil only very specific recipes that I deliberately made machine specific were being rebuilt. Now a significant amount of recipes are being unnecessarily rebuilt. I first noticed this when building Qt but this also occurs with something even simpler such as tslib. If I look at tslib's temp directory I end up seeing multiple logs for the majority of the tasks. For example I will see 4 log.do_compile logs.
> 
> I ran the sstate-diff-machines.sh script that Martin mentioned for machines defined in meta-ti and I got the below output when using tslib as the -targets:
> 
> list.M am3517-evm
> 
> http://pastebin.com/zMH8PkmP
> 
> list.M am335x-evm
> http://pastebin.com/6jbP6guA
> 
> The checksums differs for non-native recipes such as gettext, tslib and zlib.
> 
> If it matters I am using the 1.17.0 branch of bitbake since the master branch throws parsing errors.
> 
> Any suggestions on what could be the issue?

Please pick something like tslib or gettext. Find first different
checksum (do_configure is usually good for that).

# Then to compare sigdata use something like:
# $ ls sstate-diff/134934*/*/*/tslib/*do_configure*sigdata*
# it should return 2 different sigdata with 2 different sstate
# checksums, otherwise change ls expression

# $ bitbake-diffsigs sstate-diff/134934*/*/*/tslib/*do_configure*sigdata*

It will probably show some other recipe causing the difference, so just
repeat ls, bitbake-diffsigs until you find the root cause.

Cheers,

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

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

  reply	other threads:[~2013-02-06  9:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-06  8:02 Multiple MACHINE building is broken in OE-core? Cooper Jr., Franklin
2013-02-06  8:56 ` Martin Jansa [this message]
2013-02-07 18:00   ` Cooper Jr., Franklin
  -- strict thread matches above, loose matches on Subject: below --
2013-01-29  9:29 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
2013-02-10 19:02                 ` Mike Looijmans
2013-02-10 19:59                   ` Martin Jansa
2013-01-29 11:27     ` Martin Jansa

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=20130206085644.GR3271@jama \
    --to=martin.jansa@gmail.com \
    --cc=Openembedded-core@lists.openembedded.org \
    --cc=fcooper@ti.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