From: "John \(GMail\)" <john3909@gmail.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: any ETA on a working dev beagleboard demo image?
Date: Sun, 15 Nov 2009 16:08:45 -0800 [thread overview]
Message-ID: <008d01ca6650$f7d79cc0$e786d640$@com> (raw)
In-Reply-To: <alpine.LFD.2.00.0911150948430.14311@localhost>
> -----Original Message-----
> From: openembedded-devel-bounces@lists.openembedded.org
> [mailto:openembedded-devel-bounces@lists.openembedded.org] On Behalf Of
> Robert P. J. Day
> Sent: Sunday, November 15, 2009 6:57 AM
> To: OpenEmbedded Development mailing list
> Subject: [oe] any ETA on a working dev beagleboard demo image?
>
>
> yes, i know i'm sounding like a broken record, but i have an invite
> to give a short local demo of the beagleboard this tuesday and i'd
> like to do it with an angstrom development demo image, just because i
> prefer to live out there on the edge.
>
> at the moment, there is just the one package standing in the way --
> guile-native -- and as i recall, someone posted what looked like a
> manual fix. is that being turned into a patch at any point? i
> realize i'm nagging, but it's literally been *weeks* since that
> particular bitbake target actually built, and every time it looks like
> it's getting close to being buildable, more packages break.
>
> i appreciate that development means exactly that but, at the very
> least, even the development branch should *build*, even if there are
> run issues.
I also had problems building the DEV branch, but as of yesterday,
beagleboard-demo-image builds without errors on Ubuntu 9.10. I was having
problems with webkit-gtk, but Koen released a fix on Saturday and now the
build completes successfully.
>
> rday
>
> p.s. perhaps it would be useful to start tagging the development
> branch at points where it builds, just so someone can always retreat
> to the most recent known good build.
>
> or perhaps start a branch named, oh, "bleeding", which, when it builds
> properly, can be merged back into development. whatever. but it
> strikes me that it's overwhelmingly pointless to have a development
> branch that doesn't build since that gives no one the opportunity to
> actually test it.
>
> --
>
> =============================================================
> ===========
> Robert P. J. Day Waterloo, Ontario, CANADA
>
> Linux Consulting, Training and Kernel Pedantry.
>
> Web page: http://crashcourse.ca
> Twitter: http://twitter.com/rpjday
> =============================================================
> ===========
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2009-11-16 0:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-15 14:56 any ETA on a working dev beagleboard demo image? Robert P. J. Day
2009-11-16 0:00 ` Marcin Juszkiewicz
2009-11-16 0:24 ` John (GMail)
2009-11-16 9:05 ` Robert P. J. Day
2009-11-16 10:06 ` Phil Blundell
2009-11-16 10:53 ` Robert P. J. Day
2009-11-16 17:17 ` Leon Woestenberg
2009-11-16 0:08 ` John (GMail) [this message]
2009-11-16 7:58 ` Petr Štetiar
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='008d01ca6650$f7d79cc0$e786d640$@com' \
--to=john3909@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 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.