From: Radu Moisan <radu.moisan@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: dbus test suite
Date: Tue, 29 May 2012 11:29:03 +0300 [thread overview]
Message-ID: <4FC488CF.2030803@intel.com> (raw)
In-Reply-To: <1338212677.20169.75.camel@ted>
[-- Attachment #1: Type: text/plain, Size: 2652 bytes --]
On 05/28/2012 04:44 PM, Richard Purdie wrote:
> On Mon, 2012-05-28 at 14:30 +0100, Burton, Ross wrote:
>> On 28 May 2012 14:26, Andrei Gherzan<andrei@gherzan.ro> wrote:
>>> There is an internal test suite for dbus. You can enable building those
>>> tests in configure:
>>> "--enable-tests"
>> Is there a good reason why these shouldn't be always ran when building dbus?
> Well, we're cross compiling so it depends how they're written and
> whether they can run in a cross environment. We've also taken steps to
> reduce our build time so if these need something like perl or python,
> adding those into the dependency chain is problematic.
>
> I'm open to ideas here but so far they've not been useful so are likely
> disabled.
>
> Cheers,
>
> Richard
>
How do I add something in the dependency chain? With --enable-test dbus
fails at do_configure complaining about
| configure: Full test coverage was requested with --enable-tests=yes
| configure: This has many dependencies (GLib, dbus-glib, Python)
| checking for i586-poky-linux-pkg-config... no
| checking for pkg-config...
/home/radu/Documents/Development/yocto/build/tmp/sysroots/x86_64-linux/usr/bin/pkg-config
| checking pkg-config is at least version 0.9.0... yes
| checking for GLIB... yes
| checking for DBUS_GLIB... yes
| configure: Full test coverage (--enable-tests=yes) requires Python,
dbus-python, pygobject
| checking for a Python interpreter with version >= 2.6... python
| checking for python...
/home/radu/Documents/Development/yocto/build/tmp/sysroots/x86_64-linux/usr/bin/python
| checking for python version... 2.7
| checking for python platform... linux2
| checking for python script directory... ${libdir}/python2.7/site-packages
| checking for python extension module directory...
${libdir}/python2.7/site-packages
| checking for Python modules for full test coverage... Traceback (most
recent call last):
| File "<string>", line 1, in <module>
| ImportError: No module named dbus
| no
| configure: error: cannot import dbus, gobject, dbus.mainloop.glib
Python modules
| ERROR: oe_runconf failed
NOTE: package dbus-1.4.20-r3.0: task do_configure: Failed
ERROR: Task 6
(/home/radu/Documents/Development/yocto/poky/meta/recipes-core/dbus/dbus_1.4.20.bb,
do_configure) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1119 tasks of which 1118 didn't need to
be rerun and 1 failed.
Summary: 1 task failed:
/home/radu/Documents/Development/yocto/poky/meta/recipes-core/dbus/dbus_1.4.20.bb,
do_configure
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
Radu
[-- Attachment #2: Type: text/html, Size: 3780 bytes --]
next prev parent reply other threads:[~2012-05-29 8:33 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 ` Radu Moisan [this message]
2012-05-29 9:23 ` dbus test suite 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
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=4FC488CF.2030803@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