Is Angstrom dead?

Is Angstrom dead?

[Gary Thomas]

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 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"

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Is Angstrom dead?

[Graeme Gregory]

On Tue, 01 Jun 2010 06:03:09 -0600
Gary Thomas <gary@mlbassoc.com> wrote:

> It sure feels like it :-(
> 
No, we are certainly alive, but as we seem to have decreased to only 2
or 3 people who actively say they are developing Angstrom it can seem a
bit quiet at times.

Graeme

Re: Is Angstrom dead?

[Robert P. J. Day]

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
> 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

  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?

rday

-- 

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

            Linux Consulting, Training and Kernel Pedantry.

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

Re: Is Angstrom dead?

[Robert P. J. Day]

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
> masses??

  just for fun, i've updated my oe dev branch and started a build of
that same target.  we'll see if i get the same result.  and, again,
what distro are you using?  that's important to know.

rday


-- 

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

            Linux Consulting, Training and Kernel Pedantry.

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

Re: Is Angstrom dead?

[Gary Thomas]

On 06/01/2010 06:36 AM, Robert P. J. Day wrote:
> 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
>> masses??
>
>    just for fun, i've updated my oe dev branch and started a build of
> that same target.  we'll see if i get the same result.  and, again,
> what distro are you using?  that's important to know.

Fedora

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Is Angstrom dead?

[butters]

Well for me, the Gnome Image is failing. As I wrote previously without 
anyone coming up with a fix. The full gnome set was available from the 
Ångström site a couple a months ago via the image builder, now selecting 
gnome on that fails with a big red X .... It would be nice if the STABLE 
builds of things, and things that actually work, would be available in 
the image builder instead of just unstable, and it would be nice if we 
could have access to stable code instead of always bleeding edge stuff 
via OpenEmbedded.

I'm only saying this because you seem to be involved in it, so I just 
wanted to voice my opinion and get your response lol

Thanks!
Bill

On 6/1/2010 2:09 PM, Graeme Gregory wrote:
> On Tue, 01 Jun 2010 06:03:09 -0600
> Gary Thomas<gary@mlbassoc.com>  wrote:
>
>    
>> It sure feels like it :-(
>>
>>      
> No, we are certainly alive, but as we seem to have decreased to only 2
> or 3 people who actively say they are developing Angstrom it can seem a
> bit quiet at times.
>
> Graeme
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
>    

Re: Is Angstrom dead?

[Robert P. J. Day]

On Tue, 1 Jun 2010, Gary Thomas wrote:

> On 06/01/2010 06:36 AM, Robert P. J. Day wrote:
> > 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
> > > masses??
> >
> >    just for fun, i've updated my oe dev branch and started a build of
> > that same target.  we'll see if i get the same result.  and, again,
> > what distro are you using?  that's important to know.
>
> Fedora

  i just fired up bitbake for the linuxtag image, it'll take a while
and i'll let you know what happens on my ubuntu system.

rday

-- 

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

            Linux Consulting, Training and Kernel Pedantry.

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

Re: Is Angstrom dead?

[Philip Balister]

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"
>

Re: Is Angstrom dead?

[Gary Thomas]

On 06/01/2010 07:15 AM, Philip Balister wrote:
> 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.

Sure, I understand busy.  That said, I would think that _some_ reply could
be had after a week...  Also, the "busy core" Angstrom developers seem
to have lots of time to answer other, seemingly innocuous, questions on
these and other lists.

If it's not to be supported, fine; I'll just move on.  Too bad, I think
Angstrom has plenty of potential and I'd be happy to contribute (but I
need to get it going before I can!)

>>
>> 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"

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Is Angstrom dead?

[Robert P. J. Day]

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?

rday



-- 

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

            Linux Consulting, Training and Kernel Pedantry.

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

Re: Is Angstrom dead?

[Gary Thomas]

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...

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: [Angstrom-devel] Is Angstrom dead?

[Martin Jansa]

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..

Regarads,

-- 
uin:136542059                jid:Martin.Jansa@gmail.com
Jansa Martin                 sip:jamasip@voip.wengo.fr 
JaMa                         

Re: Is Angstrom dead?

[Thomas Zimmermann]

Am Dienstag 01 Juni 2010, 16:24:33 schrieb Robert P. J. Day:
> On Tue, 1 Jun 2010, Gary Thomas wrote:
> > |   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 should never depend on the pkconfig files installed on your buildhost. Are 
you sure that the gstreamer package is build?

> rday

Re: Is Angstrom dead?

[Gary Thomas]

On 06/01/2010 08:47 AM, Thomas Zimmermann wrote:
> Am Dienstag 01 Juni 2010, 16:24:33 schrieb Robert P. J. Day:
>> On Tue, 1 Jun 2010, Gary Thomas wrote:
>>> |   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 should never depend on the pkconfig files installed on your buildhost. Are
> you sure that the gstreamer package is build?

I reran my build and it passed through (no repository changes).
This particular problem seems to be a multi-threaded build (I run
with BB_NUMBER_THREADS = "4")

Sadly, the final image still does not build:

| log_check: Matched keyword: [Cannot satisfy the following dependencies]
| Collected errors:
|  * resolve_conffiles: Existing conffile /local/Angstrom_BeagleBoard/tmp/rootfs/beagleboard-linuxtag2010-demo-image/etc/device_table is different from the conffile in the new 
package. The new conffile will be placed at /local/Angstrom_BeagleBoard/tmp/rootfs/b * satisfy_dependencies_for: Cannot satisfy the following dependencies for angstrom-task-gnome:
|  *    encodings *     encodings *     encodings *
|
NOTE: package beagleboard-linuxtag2010-demo-image-1.0-r0: task do_rootfs: Failed

I don't understand this error well enough (believe me, I've
spent hours reading the various recipes and trying things)
to hazard a guess as to what this error means.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: [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
========================================================================

Re: Is Angstrom dead?

[Robert P. J. Day]

On Tue, 1 Jun 2010, Thomas Zimmermann wrote:

> Am Dienstag 01 Juni 2010, 16:24:33 schrieb Robert P. J. Day:
> > On Tue, 1 Jun 2010, Gary Thomas wrote:
> > > |   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 should never depend on the pkconfig files installed on your buildhost. Are
> you sure that the gstreamer package is build?

  my test build of the beagle linuxtag target just finished,
culminating in:

NOTE: Tasks Summary: Attempted 9996 tasks of which 7920 didn't need to be rerun and 7 failed.
ERROR: '/home/rpjday/oe/openembedded/recipes/webm/libvpx_0.9.0.bb' failed
ERROR: '/home/rpjday/oe/openembedded/recipes/ti/ti-cgt6x_6.1.9.bb' failed
ERROR: '/home/rpjday/oe/openembedded/recipes/mozilla/firefox_3.6.3.bb' failed
ERROR: '/home/rpjday/oe/openembedded/recipes/powervr-drivers/libgles-omap3_3.01.00.06.bb' failed
ERROR: '/home/rpjday/oe/openembedded/recipes/powervr-drivers/omap3-sgx-modules_1.4.14.2616.bb' failed
ERROR: '/home/rpjday/oe/openembedded/recipes/abiword/abiword_2.8.3.bb' failed
ERROR: '/home/rpjday/oe/openembedded/recipes/gnome/cheese_2.30.1.bb' failed

  i have to run off but briefly:

* i expected the firefox and abiword failures since they were failing
for beagleboard-demo-image for me

* i just did a git pull and noticed some checkins for both cheese and
gstreamer so i'll restart the build and see the difference when i get
back.

* if we're going to keep discussing this (and i'm willing to help with
the debugging), should we change the thread name?


  back in a while, when i'll look at the log files more carefully.

rday

-- 

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

            Linux Consulting, Training and Kernel Pedantry.

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

Re: [Angstrom-devel] Is Angstrom dead?

[Robert P. J. Day]

  before this thread gets any longer, would it make more sense to pick
*one* mailing list to hash this out on?  since i have some spare time
these days, i'm willing to finally dive in and try to help debug, but
it seems pointless doing this on both the OE and angstrom list.

  would the powers that be like to make a choice?  and maybe we can
have a discussion about how best to tackle outstanding bugs that
minimizes the frustration level.

  it would seem that the angstrom list, being more specific, would be
the more appropriate place.

rday

-- 

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

            Linux Consulting, Training and Kernel Pedantry.

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

Re: Is Angstrom dead?

[Graham Gower]

On 2 June 2010 00:51, Gary Thomas <gary@mlbassoc.com> wrote:
>
> I reran my build and it passed through (no repository changes).
> This particular problem seems to be a multi-threaded build (I run
> with BB_NUMBER_THREADS = "4")
>
> Sadly, the final image still does not build:
>
> | log_check: Matched keyword: [Cannot satisfy the following dependencies]
> | Collected errors:
> |  * resolve_conffiles: Existing conffile
> /local/Angstrom_BeagleBoard/tmp/rootfs/beagleboard-linuxtag2010-demo-image/etc/device_table
> is different from the conffile in the new package. The new conffile will be
> placed at /local/Angstrom_BeagleBoard/tmp/rootfs/b *
> satisfy_dependencies_for: Cannot satisfy the following dependencies for
> angstrom-task-gnome:
> |  *    encodings *     encodings *     encodings *
> |
> NOTE: package beagleboard-linuxtag2010-demo-image-1.0-r0: task do_rootfs:
> Failed
>
> I don't understand this error well enough (believe me, I've
> spent hours reading the various recipes and trying things)
> to hazard a guess as to what this error means.
>

Not understanding the error is probably because most of this error
message comes from opkg (which is a heap of crap) and part of it has
been truncated.

The first bit:
> |  * resolve_conffiles: Existing conffile
> /local/Angstrom_BeagleBoard/tmp/rootfs/beagleboard-linuxtag2010-demo-image/etc/device_table
> is different from the conffile in the new package. The new conffile will be
> placed at /local/Angstrom_BeagleBoard/tmp/rootfs/b

This indicates that multiple packages are trying to provide the
/etc/device_table config file. The message has been truncated at 256
chars - even the '\n' has been stripped so it runs on to the next
error.

I've just bumped this limit to 4096 in upstream opkg, so longer errors
should be more readable.


> satisfy_dependencies_for: Cannot satisfy the following dependencies for
> angstrom-task-gnome:
> |  *    encodings *     encodings *     encodings *

Package "angstrom-task-gnome" depends on Package "encodings", but it
cannot be found in the list of available packages. I have no idea why
its listed three times.


-Graham

Re: Is Angstrom dead?

[Gary Thomas]

On 06/01/2010 06:30 PM, Graham Gower wrote:
> On 2 June 2010 00:51, Gary Thomas<gary@mlbassoc.com>  wrote:
>>
>> I reran my build and it passed through (no repository changes).
>> This particular problem seems to be a multi-threaded build (I run
>> with BB_NUMBER_THREADS = "4")
>>
>> Sadly, the final image still does not build:
>>
>> | log_check: Matched keyword: [Cannot satisfy the following dependencies]
>> | Collected errors:
>> |  * resolve_conffiles: Existing conffile
>> /local/Angstrom_BeagleBoard/tmp/rootfs/beagleboard-linuxtag2010-demo-image/etc/device_table
>> is different from the conffile in the new package. The new conffile will be
>> placed at /local/Angstrom_BeagleBoard/tmp/rootfs/b *
>> satisfy_dependencies_for: Cannot satisfy the following dependencies for
>> angstrom-task-gnome:
>> |  *    encodings *     encodings *     encodings *
>> |
>> NOTE: package beagleboard-linuxtag2010-demo-image-1.0-r0: task do_rootfs:
>> Failed
>>
>> I don't understand this error well enough (believe me, I've
>> spent hours reading the various recipes and trying things)
>> to hazard a guess as to what this error means.
>>
>
> Not understanding the error is probably because most of this error
> message comes from opkg (which is a heap of crap) and part of it has
> been truncated.
>
> The first bit:
>> |  * resolve_conffiles: Existing conffile
>> /local/Angstrom_BeagleBoard/tmp/rootfs/beagleboard-linuxtag2010-demo-image/etc/device_table
>> is different from the conffile in the new package. The new conffile will be
>> placed at /local/Angstrom_BeagleBoard/tmp/rootfs/b
>
> This indicates that multiple packages are trying to provide the
> /etc/device_table config file. The message has been truncated at 256
> chars - even the '\n' has been stripped so it runs on to the next
> error.
>
> I've just bumped this limit to 4096 in upstream opkg, so longer errors
> should be more readable.

Yes, your change improved the readability of the messages, thanks.

That said, I'm not sure that this first part is such a problem as it also
happens when building 'beagleboard-demo-image' that does succeed.  Looking
at the results, I see these files:

$ \ls tmp/rootfs/beagleboard-*-image/etc/device_table* -l
-rw-rw-r-- 1 gthomas gthomas 1378 Jun  1 07:37 tmp/rootfs/beagleboard-demo-image/etc/device_table
-rwxr-xr-x 1 gthomas gthomas 6666 May 22 21:17 tmp/rootfs/beagleboard-demo-image/etc/device_table-opkg
-rw-rw-r-- 1 gthomas gthomas 1378 Jun  2 04:35 tmp/rootfs/beagleboard-linuxtag2010-demo-image/etc/device_table
-rwxr-xr-x 1 gthomas gthomas 6666 May 22 21:17 tmp/rootfs/beagleboard-linuxtag2010-demo-image/etc/device_table-opkg

This implies that the same conditions exist for both beagleboard-demo-image
and beagleboard-linuxtag2010-demo-image, so I'm not sure why in one case the
error checker catches it and the other not.

>
>> satisfy_dependencies_for: Cannot satisfy the following dependencies for
>> angstrom-task-gnome:
>> |  *    encodings *     encodings *     encodings *
>
> Package "angstrom-task-gnome" depends on Package "encodings", but it
> cannot be found in the list of available packages. I have no idea why
> its listed three times.

I also don't understand this one as those packages are most
certainly there:

$ tmp/sysroots/i686-linux/usr/bin/opkg-cl -f tmp/rootfs/beagleboard-linuxtag2010-demo-image/etc/opkg/opkg.conf -o tmp/rootfs/beagleboard-linuxtag2010-demo-image list 'encodings*'
encodings - 1:1.0.3-r1.0.5 - Version 1.0.3-r1.0 of package encodings
encodings-dbg - 1:1.0.3-r1.0.5 - Version 1.0.3-r1.0 of package encodings
encodings-dev - 1:1.0.3-r1.0.5 - Version 1.0.3-r1.0 of package encodings

What am I missing?

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: Is Angstrom dead?

[butters]

  Were you ever able to resolve this? I'm quite annoyed because I'm 
compiling the gnome image and still getting this error.

Thanks,
Bill

On 6/1/2010 5:21 PM, Gary Thomas wrote:
>
> Sadly, the final image still does not build:
>
> | log_check: Matched keyword: [Cannot satisfy the following dependencies]
> | Collected errors:
> |  * resolve_conffiles: Existing conffile 
> /local/Angstrom_BeagleBoard/tmp/rootfs/beagleboard-linuxtag2010-demo-image/etc/device_table 
> is different from the conffile in the new package. The new conffile 
> will be placed at /local/Angstrom_BeagleBoard/tmp/rootfs/b * 
> satisfy_dependencies_for: Cannot satisfy the following dependencies 
> for angstrom-task-gnome:
> |  *    encodings *     encodings *     encodings *
> |
> NOTE: package beagleboard-linuxtag2010-demo-image-1.0-r0: task 
> do_rootfs: Failed
>
> I don't understand this error well enough (believe me, I've
> spent hours reading the various recipes and trying things)
> to hazard a guess as to what this error means.
>

Re: Is Angstrom dead?

[Gary Thomas]

On 06/20/2010 02:23 PM, butters wrote:
> Were you ever able to resolve this? I'm quite annoyed because I'm
> compiling the gnome image and still getting this error.

Top-posting is evil...

> On 6/1/2010 5:21 PM, Gary Thomas wrote:
>>
>> Sadly, the final image still does not build:
>>
>> | log_check: Matched keyword: [Cannot satisfy the following dependencies]
>> | Collected errors:
>> | * resolve_conffiles: Existing conffile
>> /local/Angstrom_BeagleBoard/tmp/rootfs/beagleboard-linuxtag2010-demo-image/etc/device_table
>> is different from the conffile in the new package. The new conffile
>> will be placed at /local/Angstrom_BeagleBoard/tmp/rootfs/b *
>> satisfy_dependencies_for: Cannot satisfy the following dependencies
>> for angstrom-task-gnome:
>> | * encodings * encodings * encodings *
>> |
>> NOTE: package beagleboard-linuxtag2010-demo-image-1.0-r0: task
>> do_rootfs: Failed
>>
>> I don't understand this error well enough (believe me, I've
>> spent hours reading the various recipes and trying things)
>> to hazard a guess as to what this error means.

I only found a work around - the underlying problem remains.
You can fix it like this:
   % bitbake encodings -c clean
   % bitbake beagleboard-linuxtag2010-demo-image
       -or-
   % bitbake gnome-image

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------