[oe] Is Angstrom dead?
Robert P. J. Day
rpjday at crashcourse.ca
Tue Jun 1 14:32:14 CEST 2010
On Tue, 1 Jun 2010, Gary Thomas wrote:
> It sure feels like it :-(
> 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
> 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
heh. i feel your pain. there's still a couple packages that fail
to build for me for beagleboard-demo-image but as for the other issue,
i went through that yesterday in another context.
apparently (as best i understand), some distros build packages that
come with a pkg-config component, while others don't. a given build
procedure might, when trying to figure out *how* to compile a given
package, consult pkg-config. if there's no pkg-config info, what
happens is exactly what you see above, so you need to set the
corresponding vars to " " to effectively say you *know* what those
values should be and just leave pkg-config out of it. and when you
fix that, it might happen again for another package. etc, etc.
eventually, depending on your distro, you'll build up a list of env
vars that override pkg-config in some cases.
i did this yesterday for a package that allegedly builds fine on
fedora, but fails as above on ubuntu. and you didn't mention what
distro you were using. ubuntu, perhaps?
Robert P. J. Day Waterloo, Ontario, CANADA
Linux Consulting, Training and Kernel Pedantry.
Web page: http://crashcourse.ca
More information about the Openembedded-devel