All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Chris Larson <clarson@kergoth.com>
Cc: McClintock Matthew-B29882 <B29882@freescale.com>,
	Poky Project <poky@yoctoproject.org>
Subject: Re: sstate info
Date: Fri, 13 Jan 2012 08:23:30 -0700	[thread overview]
Message-ID: <4F104C72.8010605@mlbassoc.com> (raw)
In-Reply-To: <CABcZAN=HJjD8uq-00s0=_ho6DXRbEFHBEpF-jQQk0J=qGFFq8A@mail.gmail.com>

On 2012-01-12 14:12, Chris Larson wrote:
> On Thu, Jan 12, 2012 at 2:07 PM, Gary Thomas<gary@mlbassoc.com>  wrote:
>> On 2012-01-12 10:23, McClintock Matthew-B29882 wrote:
>>>
>>> On Thu, Jan 12, 2012 at 11:06 AM, Gary Thomas<gary@mlbassoc.com>    wrote:
>>>>>
>>>>> DATE is not important, that is why we are explicitly telling the
>>>>> signature to ignore this variable.
>>>>
>>>>
>>>>
>>>> It seems that DATE needs to be ignored other places as well.  Digging
>>>> further, I find:
>>>>
>>>> $ bitbake-diffsigs
>>>>
>>>> p60_poky/tmp/stamps/i686-linux/quilt-native-0.50-r0.do_patch.sigdata.216968eaca38198b88a7520be02e3fca
>>>>
>>>> p60_test_pass1/tmp/stamps/i686-linux/quilt-native-0.50-r0.do_patch.sigdata.0ce7898e700de80ff8afcb0850ec4ed0
>>>> basehash changed from 4863b21531f8236184a7c3b16da3ea13 to
>>>> 7ee430d1251148b2509ef2aefb6e5443
>>>
>>>
>>> You might just try adding to BB_HASHBASE_WHITELIST in bitbake.conf
>>> which should ignore DATE in all recipes. I thought this was there, you
>>> can check the history to see...
>>
>>
>> I'm trying this now.  Of course, touching that variable invalidates
>> the sstate cache, so I won't know until tomorrow if it works.
>
> You can't just override DATE in local.conf? I don't see the point in
> holding off, unless your builds will take till tomorrow to finish?

Actually, I didn't think of that.  I also didn't see this message
until Friday (the next day) due to some network issues, so it's moot.

That notwithstanding, I tried it today (new DATE) and it behaved as
I would like.  The only problem was that dbus-1 is still being rebuilt.
I compared the siginfo files between the two builds and they are
identical, so I don't know why.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


  parent reply	other threads:[~2012-01-13 15:23 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-12  9:57 sstate info Gary Thomas
2012-01-12 13:13 ` Martin Jansa
2012-01-12 13:31   ` Gary Thomas
2012-01-12 13:37     ` Martin Jansa
2012-01-12 15:33       ` Gary Thomas
2012-01-12 16:53         ` McClintock Matthew-B29882
2012-01-12 17:06           ` Gary Thomas
2012-01-12 17:23             ` McClintock Matthew-B29882
2012-01-12 21:07               ` Gary Thomas
2012-01-12 21:12                 ` Chris Larson
2012-01-12 21:14                   ` McClintock Matthew-B29882
2012-01-13 15:23                   ` Gary Thomas [this message]
2012-01-13 15:40                     ` McClintock Matthew-B29882
2012-01-13 16:27                       ` Richard Purdie
2012-01-13 16:53                         ` Gary Thomas
2012-01-13 17:11                           ` Gary Thomas
2012-01-14 13:30                             ` Gary Thomas
2012-01-15  0:06                               ` Richard Purdie
2012-01-13 18:09                           ` Richard Purdie
2012-01-13 18:19                             ` Gary Thomas
2012-01-13 19:36                               ` McClintock Matthew-B29882
2012-01-13 18:10                           ` Richard Purdie
2012-01-12 21:13                 ` McClintock Matthew-B29882
2012-01-12 21:28                   ` Gary Thomas

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=4F104C72.8010605@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=B29882@freescale.com \
    --cc=clarson@kergoth.com \
    --cc=poky@yoctoproject.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.