Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: gettext-native fails to build
Date: Tue, 28 Jun 2011 23:06:29 -0700	[thread overview]
Message-ID: <4E0AC0E5.2030509@gmail.com> (raw)
In-Reply-To: <w4aad19sz2.wl%peter@chubb.wattle.id.au>

On 06/28/2011 09:12 PM, Peter Chubb wrote:
>>>>>> "Khem" == Khem Raj<raj.khem@gmail.com>  writes:
>
> Khem>  On 06/28/2011 06:16 PM, Peter Chubb wrote: are you using oe.dev
> Khem>  or oe-core ?  oe-core has these races solved
>>>
>>> oe.dev.  I'll try again with the core branch.
>>>
> Khem>  FWIW here are my notes on how to use oe-core for angstrom
>
> Khem>  http://sakrah.homelinux.org/blog/2011/03/using-openembedded-core-to-build-angstrom-for-qemu/
>
> Thanks.
>
> It looks as though oe-core doesn't know about collie yet.  I copied
> the machine description from oe-dev, and am attempting to build
> console-image.  Is there a graphical PIM image that's likely to build
> and work?

May be you can try core-image-sato

> --
> Dr Peter Chubb  http://www.gelato.unsw.edu.au  peterc AT gelato.unsw.edu.au
> http://www.ertos.nicta.com.au           ERTOS within National ICT Australia
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel




      reply	other threads:[~2011-06-29  6:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29  0:25 gettext-native fails to build Peter Chubb
2011-06-29  0:33 ` Peter Chubb
2011-06-29  1:06 ` Khem Raj
2011-06-29  1:16   ` Peter Chubb
2011-06-29  1:38     ` Khem Raj
2011-06-29  4:12       ` Peter Chubb
2011-06-29  6:06         ` Khem Raj [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=4E0AC0E5.2030509@gmail.com \
    --to=raj.khem@gmail.com \
    --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