All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jack Mitchell <ml@communistcode.co.uk>
To: yocto@yoctoproject.org
Subject: Re: proper recipe for building for beagle xM? meta-ti?
Date: Mon, 05 Mar 2012 09:52:00 +0000	[thread overview]
Message-ID: <4F548CC0.4050802@communistcode.co.uk> (raw)
In-Reply-To: <alpine.DEB.2.02.1203041629001.18196@oneiric>

On 04/03/12 21:38, Robert P. J. Day wrote:
> On Sun, 4 Mar 2012, Gary Thomas wrote:
>
>> Can you explain what the toolchain problems are and why the versions
>> in oe-core don't work for meta-ti?
>
>    i just finished doing a "bitbake core-image-minimal" for a
> beagleboard using the meta-ti layer, and having only to set a
> preferred version for udev.
>
>    the build finished (albeit with a few warnings), and i have all of
> the images i would expect for a beagle xM.  should i consider this a
> form of success -- the simple fact that the build appeared to succeed?
>
> rday
>

Does it boot? I would expect this to be the next test? If you don't have 
a beagleboard to test if you host it somewhere I can give it quick go 
later today if I get time.

Regards,

-- 

   Jack Mitchell (jack@embed.me.uk)
   Embedded Systems Engineer
   http://www.embed.me.uk

--



  parent reply	other threads:[~2012-03-05  9:51 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-28 18:51 proper recipe for building for beagle xM? meta-ti? Robert P. J. Day
2012-02-28 21:22 ` Bruce Ashfield
2012-02-28 21:55   ` Robert P. J. Day
2012-02-28 22:09     ` Koen Kooi
2012-02-28 22:28       ` Robert P. J. Day
2012-03-02 10:06         ` Koen Kooi
2012-03-02 16:45           ` Stewart, David C
2012-03-02 16:51             ` Robert P. J. Day
2012-03-02 17:15             ` Koen Kooi
2012-03-02 22:22         ` William Mills
2012-03-02 22:33           ` Robert P. J. Day
2012-03-02 22:50             ` William Mills
2012-03-02 23:18               ` Gary Thomas
2012-03-03  0:07                 ` William Mills
2012-03-04  6:18                 ` Denys Dmytriyenko
2012-03-04 12:19                   ` Robert P. J. Day
2012-03-04 12:36                     ` Gary Thomas
2012-03-04 12:54                       ` Robert P. J. Day
2012-03-04 17:01                         ` Koen Kooi
2012-03-04 18:14                       ` Robert P. J. Day
2012-03-04 19:27                         ` Denys Dmytriyenko
2012-03-04 19:43                           ` Robert P. J. Day
2012-03-04 19:45                           ` Gary Thomas
2012-03-04 20:01                             ` Brian Hutchinson
2012-03-04 20:04                             ` Denys Dmytriyenko
2012-03-04 21:18                               ` Robert P. J. Day
2012-03-05  5:12                                 ` [yocto] " Denys Dmytriyenko
2012-03-05 11:00                                   ` Robert P. J. Day
2012-03-04 21:38                             ` Robert P. J. Day
2012-03-05  4:26                               ` Denys Dmytriyenko
2012-03-05  9:52                               ` Jack Mitchell [this message]
2012-03-04  6:08           ` Denys Dmytriyenko
2012-02-28 22:12     ` Bruce Ashfield

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=4F548CC0.4050802@communistcode.co.uk \
    --to=ml@communistcode.co.uk \
    --cc=yocto@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 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.