[oe] [Angstrom-devel] Is Angstrom dead?

[Robert P. J. Day]

On Tue, 1 Jun 2010, Martin Jansa wrote:

> On Tue, Jun 01, 2010 at 10:24:33AM -0400, 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?
>
> It says:
> > > | No package 'gstreamer-plugins-base-0.10' found
>
> was gstreamer-plugins-base built before building cheese? It's only
> in RRECOMMENDS so if it's now in latest version required dependency
> then gstreamer should be moved to DEPENDS (to make sure it's built
> before do_configure of cheese.
>
> Or it cannot find pkgconfig from gstreamer-plugins-base, I don't see
> why it should look from its own pkgconfig file..

  i can't comment on that and i could be entirely off-base here.  i'm
simply pointing out that, ironically, i had *exactly* this issue
yesterday with a different software package -- running the initial
"configure" step expected to find that package's pkgconfig info and,
if it wasn't there, the configure failed.  the only way around it was
(exactly as above) to set the variables *_CFLAGS and *_LIBS manually,
which would override the configuration's attempt to query pkconfig for
that info.

  as i said, i could be *completely* wrong.  but this is what i dealt
with yesterday, and that's how i fixed it.

rday

-- 

========================================================================
Robert P. J. Day                               Waterloo, Ontario, CANADA

            Linux Consulting, Training and Kernel Pedantry.

Web page:                                          http://crashcourse.ca
Twitter:                                       http://twitter.com/rpjday
========================================================================