All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Is Angstrom dead?
Date: Tue, 01 Jun 2010 09:21:40 -0600	[thread overview]
Message-ID: <4C052584.2040905@mlbassoc.com> (raw)
In-Reply-To: <201006011647.23770.ml@vdm-design.de>

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



  reply	other threads:[~2010-06-01 15:25 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
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 [this message]
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=4C052584.2040905@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.