Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: glib-2.0_2.26.1 missing dependency on dbus
Date: Wed, 8 Dec 2010 06:32:40 +0100	[thread overview]
Message-ID: <20101208053240.GD3186@jama> (raw)

Hi,

simply adding it to depends create circular dependency

bitbake@jama ~/dev/recipes $ grep glib dbus/dbus.inc 
DEPENDS = "expat glib-2.0 virtual/libintl libsm libice virtual/libx11"

dbus needs glib it only for dbus-viewer and builds ok without glib, so
I've removed glib-2.0 in dbus and added dbus to glib-2.0_2.26.1 and 
tried again...

These are usually caused by circular dependencies and any circular 
dependency chains found will be printed below. Increase the debug 
level to see a list of unbuildable tasks.

It didn't detect it.. so I had to find it manually:
bitbake@jama ~/dev/recipes $ grep glib dbus/dbus.inc
DEPENDS = "expat glib-2.0 virtual/libintl libsm libice virtual/libx11"

bitbake@jama ~/dev/recipes $ grep util-linux-ng xorg-lib/libsm_1.2.0.bb
DEPENDS += "libice xproto xtrans util-linux-ng"
bitbake@jama ~/dev/recipes $ grep udev util-linux-ng/util-linux-ng.inc
DEPENDS = "${@base_contains('DISTRO_FEATURES', 'pam', 'libpam', '', d)} udev  zlib ncurses virtual/libintl"
bitbake@jama ~/dev/recipes $ grep glib udev/udev_151.bb
# Needed for udev-extras
DEPENDS = "gperf-native usbutils acl glib-2.0"

util-linux-ng seems to build fine without udev but is there better place
to break this curcular dependency?

Regards,



             reply	other threads:[~2010-12-08  5:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08  5:32 Martin Jansa [this message]
2010-12-20  2:53 ` glib-2.0_2.26.1 missing dependency on dbus Khem Raj
2010-12-22  8:27 ` 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=20101208053240.GD3186@jama \
    --to=martin.jansa@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox