All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>
Cc: Poky <poky@lists.pokylinux.org>
Subject: Re: Unable to build
Date: Tue, 06 Mar 2012 06:26:25 -0800	[thread overview]
Message-ID: <1331043985.25887.8.camel@ted> (raw)
In-Reply-To: <4F5616AB.6000603@mlbassoc.com>

On Tue, 2012-03-06 at 06:52 -0700, Gary Thomas wrote:
> After a recent update, I'm now getting this error in a previously
> working setup.
> 
> ERROR:  OE-core's config sanity checker detected a potential misconfiguration.
>      Either fix the cause of this error or at your own risk disable the checker (see sanity.conf).
>      Following is the list of potential problems / advisories:
> 
>      Your configuration is using stamp files including the sstate hash but your build directory was built with stamp files that do not include this.
> To continue, either rebuild or switch back to the OEBasic signature handler with BB_SIGNATURE_HANDLER = 'OEBasic'.
> 
> I'm using my own distro.conf (not poky.conf), and I'm not setting
> BB_SIGNATURE_HANDLER anywhere, so I think it should already be
> set to OEBasic.  I even tried to put that line (cut & pasted
> from the error message) in local.conf - no change.
> 
> How can I get past this, short of a complete rebuild?

You've somehow merged a change like:

http://git.yoctoproject.org/cgit.cgi/poky/commit/meta-yocto?id=ea2c8defd570bc2c4d29c6b0bd9fd84865d4e144

which sets OELAYOUT_ABI = "8" and triggers the transition message about
OEBasicHash. Set it to "7" and it won't show that message.

Cheers,

Richard




  reply	other threads:[~2012-03-06 14:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-06 13:52 Unable to build Gary Thomas
2012-03-06 14:26 ` Richard Purdie [this message]
2012-03-06 14:33   ` Gary Thomas
2012-03-07 20:12     ` Richard Purdie
2012-03-07 21:31       ` 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=1331043985.25887.8.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=gary@mlbassoc.com \
    --cc=poky@lists.pokylinux.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.