From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Poor first impression
Date: Wed, 22 May 2013 05:57:49 -0600 [thread overview]
Message-ID: <519CB2BD.4040604@mlbassoc.com> (raw)
In-Reply-To: <1369177001.3843.9.camel@ted>
On 2013-05-21 16:56, Richard Purdie wrote:
> On Tue, 2013-05-21 at 12:13 -0600, Gary Thomas wrote:
>> On 2013-05-21 03:10, Richard Purdie wrote:
>>> On Fri, 2013-05-17 at 07:26 -0600, 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...
>>>
>>> There are two issues there, firstly the scripts/bitbake binary is doing
>>> a really bad job, secondly, one of the improved debugging patches I
>>> added to bitbake, regressed things in this case.
>>>
>>> I posted a patch to bitbake last night, I've just posted a fix for
>>> scripts/bitbake now. These two together should improve this. I agree
>>> that particular error would create a poor first impression, thanks for
>>> reporting it.
>>
>> With this patch, no 'git' and a fresh build I still get this:
>>
>> Traceback (most recent call last):
>> File "/home/local/poky-multi/bitbake/bin/bitbake", line 293, in <module>
>> ret = main()
>> File "/home/local/poky-multi/bitbake/bin/bitbake", line 260, in main
>> event = server.event_queue.get(block=False)
>> File "/usr/lib/python2.6/multiprocessing/queues.py", line 104, in get
>> raise Empty
>> Empty
>> Pseudo is not present but is required, building this first before the main build
>> Traceback (most recent call last):
>> File "/home/local/poky-multi/bitbake/bin/bitbake", line 293, in <module>
>> ret = main()
>> File "/home/local/poky-multi/bitbake/bin/bitbake", line 260, in main
>> event = server.event_queue.get(block=False)
>> File "/usr/lib/python2.6/multiprocessing/queues.py", line 104, 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: git
>>
>> Still not very pretty.
>
>
> Did you apply both patches, the one for bitbake and the one for OE-Core?
> This looks like the bitbake one is missing.
Sorry, I missed that since they went to different mailing lists.
The output is much cleaner with the other patch.
Thanks
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
prev parent reply other threads:[~2013-05-22 11:57 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
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 [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=519CB2BD.4040604@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=openembedded-core@lists.openembedded.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 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.