From: Ed Nelson <enelson1000@comcast.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Release-2010.12 build failure - eglibc do_package Failed
Date: Thu, 09 Dec 2010 09:06:22 -0800 [thread overview]
Message-ID: <4D010C8E.1080309@comcast.net> (raw)
In-Reply-To: <4D01096E.6010105@eukrea.com>
On 12/9/2010 8:53 AM, Eric Bénard wrote:
> On 09/12/2010 17:15, Ed Nelson wrote:
>> On 12/9/2010 7:49 AM, Eric Bénard wrote:
>>> Hi,
>>>
>>> On 09/12/2010 16:44, Ed Nelson wrote:
>>>> I am using the latest release-2010.12 and doing a completely new
>>>> build for the
>>>> AT91SAM9g20 development board(no tmp directory and source directory
>>>> empty).
>>>> I am trying to build a base image that includes python.
>>>> My build machine is running Ubuntu 10.04LTS.
>>>>
>>> are you runing Ubuntu as the native OS on the machine or in a virtual
>>> machine (VirtualBox for example) ?
>>>
>>> Eric
>>>
>> I am using on Native machine
>>
> ok I have the same problem on virtual machines running Ubuntu 10.04 &
> 10.10.
> I have to test a VirtualBox with an other distribution to see if the
> problem comes from the virtualmachine or Ubuntu 10.04 & 10.10.
>
> Setting PREFERRED_VERSION_qemu-native = "0.12.5" "solved" the problem
> here.
>
> Eric
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>
Did you add that to the local.conf file or somewhere else?
Thanks
Ed
next prev parent reply other threads:[~2010-12-09 17:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 15:44 Release-2010.12 build failure - eglibc do_package Failed Ed Nelson
2010-12-09 15:49 ` Eric Bénard
2010-12-09 16:15 ` Ed Nelson
2010-12-09 16:53 ` Eric Bénard
2010-12-09 17:06 ` Ed Nelson [this message]
2010-12-09 18:43 ` Ed Nelson
2010-12-10 23:12 ` Tim Harvey
2010-12-09 17:00 ` Tim Harvey
2010-12-09 17:07 ` Martin Jansa
2010-12-09 18:00 ` Yury Bushmelev
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=4D010C8E.1080309@comcast.net \
--to=enelson1000@comcast.net \
--cc=openembedded-devel@lists.openembedded.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