Merciadri Luca wrote: > Philip Balister wrote: > >> On 06/01/2010 10:47 AM, Merciadri Luca wrote: >> >>> Gary Thomas wrote: >>> >>>> On 06/01/2010 08:24 AM, Robert P. J. Day wrote: >>>> >>>>> On Tue, 1 Jun 2010, Gary Thomas wrote: >>>>> >>>>> >>>>>> 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 >>>>>> >>>>> now i'm slightly confused since neither ubuntu or fedora appear to >>>>> have any pkgconfig info for the cheese package, so why would there be >>>>> a test for it that you would need to override? or is this not >>>>> pkgconfig-related? >>>>> >>>> I've no idea - all I was pointing out is that as of this morning, >>>> there's a new failure... >>>> >>>> >>> It is not dead. The problem is that there is a small linux community, >>> and an even smaller Angström community, and, in this community, only a >>> slight part is composed of gurus. At least, that's my POV. >>> >>> >> And as I noted on the OE list, the gurus are picking up paid work that >> cuts into our time. This is good for Angstrom in the long term, but >> does cut into our response times. Please feel free to step up and >> start working through the problems, everyone starts on the path to >> becoming a guru slowly. >> > You might already realize that I am the author of Angström's manual; > http://gitorious.org/angstrom-manual. If I had some spare time, I would > surely participate more in the project. > >
-- Merciadri Luca _______________________________________________ Debian-eeepc-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/debian-eeepc-devel
