From: Radu Moisan <radu.moisan@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: dbus test suite
Date: Tue, 29 May 2012 14:18:39 +0300 [thread overview]
Message-ID: <4FC4B08F.40207@intel.com> (raw)
In-Reply-To: <4FC499E9.6090108@windriver.com>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
On 05/29/2012 12:42 PM, Florin Sarbu wrote:
> that would be dbus-glib you need at this point as Andrei pointed out,
> not python-dbus
dbus-glib and python-dbus are building fine (with --disable-tests),
however dbus is still crushing in do_configure (same way as before). The
question is, where do I add these libraries as dependencies for dbus,
because I assume they have to be somehow inserted into the dependency
chain. This happens when I use --enable-tests (the whole test suite).
When I use --enable-embedded-tests or --enable-modular-tests or
--enable-installed-tests (all of wich are subsets of the whole test
suite) I get no complaints about missing dependency, instead it crashes
at do_compile because of missing dbus/dbus-glib-lowlevel.h
Radu
[-- Attachment #2: Type: text/html, Size: 1569 bytes --]
next prev parent reply other threads:[~2012-05-29 11:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 10:55 [PATCH 0/3] Package Updates Burton, Ross
2012-05-28 11:21 ` Radu Moisan
2012-05-28 11:21 ` Andrei Gherzan
2012-05-28 12:07 ` Paul Eggleton
2012-05-28 13:24 ` Radu Moisan
2012-05-28 13:26 ` Andrei Gherzan
2012-05-28 13:30 ` Burton, Ross
2012-05-28 13:44 ` Richard Purdie
2012-05-28 13:47 ` Burton, Ross
2012-05-28 13:58 ` Andrei Gherzan
2012-05-29 12:10 ` Philip Balister
2012-05-29 14:04 ` Radu Moisan
2012-05-29 8:29 ` dbus test suite Radu Moisan
2012-05-29 9:23 ` Radu Moisan
2012-05-29 9:28 ` Andrei Gherzan
2012-05-29 9:41 ` Radu Moisan
2012-05-29 9:42 ` Florin Sarbu
2012-05-29 11:18 ` Radu Moisan [this message]
2012-05-29 6:28 ` [PATCH 0/3] Package Updates Radu Moisan
2012-05-29 6:58 ` Radu Moisan
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=4FC4B08F.40207@intel.com \
--to=radu.moisan@intel.com \
--cc=openembedded-core@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