Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Is Angstrom dead?
Date: Tue, 01 Jun 2010 09:15:11 -0400	[thread overview]
Message-ID: <4C0507DF.8080707@balister.org> (raw)
In-Reply-To: <4C04F6FD.4070804@mlbassoc.com>

On 06/01/2010 08:03 AM, Gary Thomas wrote:
> It sure feels like it :-(

More that the core Angstrom devs are really popular people so we have 
lots of work at the moment.

Philip


>
> For a week, I've been trying to build various images in Angstrom
> and the problems I've faced have gone totally unanswered on either
> the Angstrom or OE mailing lists. I'm not the only one facing
> these problems either.
>
> I'm mostly interested in building beagleboard-linuxtag2010-demo-image
> which [at least] implies it should be a great demo to show at
> LinuxTag (which starts in only a few days now). Surely a show
> piece would be something that a popular project would want to
> support and be available to the masses??
>
> I tried again today, updating to org.openembedded.dev branch,
> commit a2834c64fb3ed535fca51c25547754fa907e4ca5 Sadly, new
> problems (and probably still the old ones) remain:
>
> | checking for CHEESE... configure: error: Package requirements (
> glib-2.0 >= 2.16.0 gobject-2.0 >= 2.12.0 gio-2.0 >= 2.16.0 gtk+-2.0 >=
> 2.19.1 gdk-2.0 >= 2.14.0 gnome-desktop-2.0 >= 2.26.0 gconf-2.0 >= 2.16.0
> gstreamer-0.10 >= 0.10.23 gstreamer-plugins-base-0.10 >= 0.10.23 cairo
>  >= 1.4.0 dbus-1 >= 1.0 dbus-glib-1 >= 0.7 pangocairo >= 1.18.0
> librsvg-2.0 >= 2.18.0
> | libcanberra-gtk gudev-1.0) were not met:
> |
> | No package 'gstreamer-plugins-base-0.10' found
> |
> | Consider adjusting the PKG_CONFIG_PATH environment variable if you
> | installed software in a non-standard prefix.
> |
> | Alternatively, you may set the environment variables CHEESE_CFLAGS
> | and CHEESE_LIBS to avoid the need to call pkg-config.
> | See the pkg-config man page for more details.
> |
> NOTE: package cheese-2.30.1-r0: task do_configure: Failed
>
> Nothing special - out of the box config file with
> MACHINE="beagleboard"
> DISTRO="angstrom-2008.1"
>



  parent reply	other threads:[~2010-06-01 13:19 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 12:03 Is Angstrom dead? Gary Thomas
2010-06-01 12:09 ` Graeme Gregory
2010-06-01 12:41   ` butters
2010-06-01 12:32 ` Robert P. J. Day
2010-06-01 12:36 ` Robert P. J. Day
2010-06-01 12:39   ` Gary Thomas
2010-06-01 12:48     ` Robert P. J. Day
2010-06-01 13:15 ` Philip Balister [this message]
2010-06-01 13:35   ` Gary Thomas
2010-06-01 14:24 ` Robert P. J. Day
2010-06-01 14:34   ` Gary Thomas
2010-06-01 14:46   ` [Angstrom-devel] " Martin Jansa
2010-06-01 15:34     ` Robert P. J. Day
2010-06-01 18:38       ` Robert P. J. Day
2010-06-01 14:47   ` Thomas Zimmermann
2010-06-01 15:21     ` Gary Thomas
2010-06-02  0:30       ` Graham Gower
2010-06-02 11:00         ` Gary Thomas
2010-06-20 20:23       ` butters
2010-06-20 20:34         ` Gary Thomas
2010-06-01 16:14     ` Robert P. J. Day

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=4C0507DF.8080707@balister.org \
    --to=philip@balister.org \
    --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