From: Darren Hart <dvhart@linux.intel.com>
To: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: DISTRO 'poky' not found
Date: Mon, 14 Mar 2011 14:49:31 -0700 [thread overview]
Message-ID: <4D7E8D6B.1020209@linux.intel.com> (raw)
In-Reply-To: <4D7E88AC.5060809@linux.intel.com>
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.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-03-14 21:49 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 [this message]
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
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=4D7E8D6B.1020209@linux.intel.com \
--to=dvhart@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox