All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Problems building Angstrom images
Date: Thu, 27 May 2010 05:14:10 -0600	[thread overview]
Message-ID: <4BFE5402.8030607@mlbassoc.com> (raw)

A number of images in the current tree (8bb53d3f261c59353652f0328bfd887d6aa1c112)
won't build, yielding errors like these:

| 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

To be clear, I'm building
   MACHINE="beagleboard"
   DISTRO="angstrom-2008.1"

I got these errors when I tried to build:
   beagleboard-linuxtag2010-demo-image
   angstrom-gnome-image

I have success with
   beagleboard-demo-image

Any ideas how to fix this?

Thanks

n.b. yes, this is a cross post from the Angstrom list, but my
query sat there for a day with no reply and I'm hoping for some
help from the larger OE crew

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



             reply	other threads:[~2010-05-27 11:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 11:14 Gary Thomas [this message]
2010-05-28  9:40 ` Problems building Angstrom images gideon
2010-05-28 11:44   ` Gary Thomas
2010-06-12 12:37     ` Jacinto Alvarez
2010-06-12 13:19       ` Gary Thomas
2010-06-12 14:36         ` Jacinto Alvarez
2010-06-14  9:29 ` Enrico Scholz
2010-06-14  9:47   ` Koen Kooi

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=4BFE5402.8030607@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.