From: Gary Thomas <gary@mlbassoc.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Poor first impression
Date: Fri, 17 May 2013 08:23:52 -0600 [thread overview]
Message-ID: <51963D78.8010908@mlbassoc.com> (raw)
In-Reply-To: <51963C52.1040004@linux.intel.com>
On 2013-05-17 08:18, Saul Wold wrote:
> On 05/17/2013 04:26 PM, Gary Thomas wrote:
>> I just tried to run Poky/Yocto on a fresh Ubuntu 12.04 system. I knew
>> there would
>> be missing bits and have seen the "sanity" messages in the past, so I
>> thought I'd
>> just carry on. Today's experience was not pretty and would it not for
>> my experience
>> with this, I would have been very perplexed...
>>
>
> Hey Gary, was this on a 1.4 / Danny Branch or master? Richard may have done something with master when he made some of the Python3 changes.
Master, updated 2013-05-16
>> Here's what I saw:
>>
>> gthomas@saturn:/local/qemuarm_poky$ bitbake core-image-sato
>> /local/poky-multi/scripts/bitbake: 1: /local/poky-multi/scripts/bitbake:
>> git: not found
>> File "<string>", line 1
>> from distutils.version import LooseVersion; import sys;
>> sys.exit(not (LooseVersion('>=') 1.7.5 LooseVersion('')))
>> ^
>> SyntaxError: invalid syntax
>> /local/poky-multi/scripts/bitbake: 1: /local/poky-multi/scripts/bitbake:
>> git: not found
>> File "<string>", line 1
>> from distutils.version import LooseVersion; import sys;
>> sys.exit(not (LooseVersion('>=') 1.7.5 LooseVersion('')))
>> ^
>> SyntaxError: invalid syntax
>> Traceback (most recent call last):
>> File "/local/poky-multi/bitbake/bin/bitbake", line 293, in <module>
>> ret = main()
>> File "/local/poky-multi/bitbake/bin/bitbake", line 260, in main
>> event = server.event_queue.get(block=False)
>> File "/usr/lib/python2.7/multiprocessing/queues.py", line 134, in get
>> raise Empty
>> Empty
>> Pseudo is not present but is required, building this first before the
>> main build
>> ^CTraceback (most recent call last):
>> File "/local/poky-multi/bitbake/bin/bitbake", line 293, in <module>
>> ret = main()
>> File "/local/poky-multi/bitbake/bin/bitbake", line 260, in main
>> event = server.event_queue.get(block=False)
>> File "/usr/lib/python2.7/multiprocessing/queues.py", line 134, in get
>> raise Empty
>> Empty
>> 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:
>>
>> Please install the following missing utilities: C++ Compiler
>> (g++),diffstat,makeinfo,git,gawk,chrpath
>>
>> ERROR: Execution of event handler 'check_sanity_eventhandler' failed
>>
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2013-05-17 14:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 13:26 Poor first impression Gary Thomas
2013-05-17 14:18 ` Saul Wold
2013-05-17 14:23 ` Gary Thomas [this message]
2013-05-17 14:32 ` Burton, Ross
2013-05-17 15:03 ` Gary Thomas
2013-05-21 9:10 ` Richard Purdie
2013-05-21 18:13 ` Gary Thomas
2013-05-21 22:56 ` Richard Purdie
2013-05-22 11:57 ` 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=51963D78.8010908@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.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 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.