Poky Project Discussions
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: poky@yoctoproject.org
Subject: Re: DISTRO 'poky' not found
Date: Wed, 16 Mar 2011 12:11:37 -0700	[thread overview]
Message-ID: <4D810B69.4000409@linux.intel.com> (raw)
In-Reply-To: <1300291497.30423.1887.camel@rex>



On 03/16/2011 09:04 AM, Richard Purdie wrote:
> On Wed, 2011-03-16 at 09:01 -0700, Darren Hart wrote:
>>
>> On 03/15/2011 02:40 AM, Joshua Lock wrote:
>>> On Mon, 2011-03-14 at 14:49 -0700, Darren Hart wrote:
>>>>
>>>> On 03/14/2011 02:29 PM, Darren Hart wrote:
>>>>> I've run into this error several times during development of various things. It will be in a build tree that I have been working with for a while, then when I come back to it, I get the following. Any idea what triggers this? I suspect something in my workflow, but I can't imagine what it would be. I'd really like to not have to delete my build tree.
>>>>>
>>>>> $ cd poky.git
>>>>> $ source poky-init-build-env build-qemux86/
>>>>>
>>>>> ### Shell environment set up for Poky builds. ###
>>>>>
>>>>> You can now run 'bitbake<target>'
>>>>>
>>>>> Common targets are:
>>>>>        poky-image-minimal
>>>>>        poky-image-sato
>>>>>        meta-toolchain
>>>>>        meta-toolchain-sdk
>>>>>
>>>>> You can also run generated qemu images with a command like 'poky-qemu qemux86'
>>>>>
>>>>> $ bitbake linux-yocto
>>>>> ERROR:  Poky'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:
>>>>>
>>>>>        Please set TARGET_OS directly, or choose a MACHINE or DISTRO that does so.
>>>>> DISTRO 'poky' not found. Please set a valid DISTRO in your local.conf
>>>>
>>>>
>>>> Thanks to Beth and Mark who pointed me in the right direction. This
>>>> appears to be a problem with master, if I cherry-pick my changes on top
>>>> of the bernard branch, the build continues as expected.
>>>>
>>>
>>> Ah, our layers.conf.sample doesn't include the new meta-yocto layer. So
>>> I'm guessing this is a clean build dir?
>>
>> I believe I've seen it on both - but probably only when switching
>> branches back and forth between master and bernard.
>
> There should be a fix in master for this now though?

I believe so yes, the meta-yocto thing from Josh. I'll holler if I hit 
it again with that in place.

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel


      reply	other threads:[~2011-03-16 19:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 21:29 DISTRO 'poky' not found Darren Hart
2011-03-14 21:49 ` Darren Hart
2011-03-15  9:40   ` Joshua Lock
2011-03-16 16:01     ` Darren Hart
2011-03-16 16:04       ` Richard Purdie
2011-03-16 19:11         ` Darren Hart [this message]

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=4D810B69.4000409@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=poky@yoctoproject.org \
    --cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox