Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Radu Moisan <radu.moisan@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: dbus test suite
Date: Tue, 29 May 2012 12:41:24 +0300	[thread overview]
Message-ID: <4FC499C4.8000904@intel.com> (raw)
In-Reply-To: <CAK18fxFZ_rYXEeeaLwH1Npx=f6dUJw2LHiKxkBg=OKm6=yAhEQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 6379 bytes --]


On 05/29/2012 12:28 PM, Andrei Gherzan wrote:
> On Tue, May 29, 2012 at 12:23 PM, Radu Moisan <radu.moisan@intel.com 
> <mailto:radu.moisan@intel.com>> wrote:
>
>
>     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
>
>
> This says that the configure cannot find the dbus python module. This 
> is created in the python-dbus package. So compile that first.
>
>>
>>
>>     Radu
>>
>     Leaving --enable-tests aside for a moment, I'm trying to build
>     dbus with --enable-embedded-tests which is less but still good
>     instead of nothing. However, the build fails at do_compile
>     complaining about dbus/dbus-glib-lowlevel.h missing, although it's
>     there. So I think some variable in Makefile is not pointing
>     correctly, but I cannot find which.
>
>     | i586-poky-linux-libtool: link: i586-poky-linux-ar cru
>     .libs/libdbus-testutils.a .libs/test-utils.o
>     | i586-poky-linux-libtool: link: i586-poky-linux-ranlib
>     .libs/libdbus-testutils.a
>     | i586-poky-linux-libtool: link: ( cd ".libs" && rm -f
>     "libdbus-testutils.la <http://libdbus-testutils.la>" && ln -s
>     "../libdbus-testutils.la <http://libdbus-testutils.la>"
>     "libdbus-testutils.la <http://libdbus-testutils.la>" )
>     | dbus-daemon.c:32:37: fatal error: dbus/dbus-glib-lowlevel.h: No
>     such file or directory
>     | compilation terminated.
>     | i586-poky-linux-libtool: link: ccache i586-poky-linux-gcc -m32
>     -march=i586
>     --sysroot=/home/radu/Documents/Development/yocto/build/tmp/sysroots/qemux86
>     -Wall -Wchar-subscripts -Wmissing-declarations
>     -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align
>     -Wno-address -Wfloat-equal -Wdeclaration-after-statement
>     -Wno-unused -Wno-sign-compare -Wno-pointer-sign
>     -Wno-deprecated-declarations -fno-common -fno-strict-aliasing -O2
>     -pipe -g -feliminate-unused-debug-types -Wl,-O1
>     -Wl,--hash-style=gnu -Wl,--as-needed -o test-segfault test-segfault.o
>     | make[3]: *** [test_dbus_daemon-dbus-daemon.o] Error 1
>     | make[3]: *** Waiting for unfinished jobs....
>     | i586-poky-linux-libtool: link: ccache i586-poky-linux-gcc -m32
>     -march=i586
>     --sysroot=/home/radu/Documents/Development/yocto/build/tmp/sysroots/qemux86
>     -Wall -Wchar-subsERROR: Function failed: do_compile (see
>     /home/radu/Documents/Development/yocto/build/tmp/work/i586-poky-linux/dbus-1.4.20-r3.0/temp/log.do_compile.10606
>     for further information)
>     | cripts -Wmissing-declarations -Wmissing-prototypes
>     -Wnested-externs -Wpointer-arith -Wcast-align -Wno-address
>     -Wfloat-equal -Wdeclaration-after-statement -Wno-unused
>     -Wno-sign-compare -Wno-pointer-sign -Wno-deprecated-declarations
>     -fno-common -fno-strict-aliasing -O2 -pipe -g
>     -feliminate-unused-debug-types -Wl,-O1 -Wl,--hash-style=gnu
>     -Wl,--as-needed -o test-exit test-exit.o
>     | i586-poky-linux-libtool: link: ccache i586-poky-linux-gcc -m32
>     -march=i586
>     --sysroot=/home/radu/Documents/Development/yocto/build/tmp/sysroots/qemux86
>     -Wall -Wchar-subscripts -Wmissing-declarations
>     -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align
>     -Wno-address -Wfloat-equal -Wdeclaration-after-statement
>     -Wno-unused -Wno-sign-compare -Wno-pointer-sign
>     -Wno-deprecated-declarations -fno-common -fno-strict-aliasing -O2
>     -pipe -g -feliminate-unused-debug-types -Wl,-O1
>     -Wl,--hash-style=gnu -Wl,--as-needed -o test-sleep-forever
>     test-sleep-forever.o
>     | loopback.c:32:37: fatal error: dbus/dbus-glib-lowlevel.h: No
>     such file or directory
>     | compilation terminated.
>     | make[3]: *** [test_loopback-loopback.o] Error 1
>     | i586-poky-linux-libtool: link: ccache i586-poky-linux-gcc -m32
>     -march=i586
>     --sysroot=/home/radu/Documents/Development/yocto/build/tmp/sysroots/qemux86
>     -Wall -Wchar-subscripts -Wmissing-declarations
>     -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align
>     -Wno-address -Wfloat-equal -Wdeclaration-after-statement
>     -Wno-unused -Wno-sign-compare -Wno-pointer-sign
>     -Wno-deprecated-declarations -fno-common -fno-strict-aliasing -O2
>     -pipe -g -feliminate-unused-debug-types -Wl,-O1
>     -Wl,--hash-style=gnu -Wl,--as-needed -o spawn-test spawn-test.o 
>     ../dbus/.libs/libdbus-internal.a -lpthread -lrt
>     | corrupt.c:33:37: fatal error: dbus/dbus-glib-lowlevel.h: No such
>     file or directory
>
>
> You will need dbus-glib. This is the package which provides this 
> header. This will be a dependency for your case.
>
> Hope i gave to the right hints. If you need more detailed info just 
> ping me.
>
> @g
>
tried to compile python-dbus already but ended up with the second 
failure about missing dbus/dbus-glib-lowlevel.h (that's when I started 
experimenting with --enable-embedded-tests and --enable-modular-tests).

Radu

[-- Attachment #2: Type: text/html, Size: 9921 bytes --]

  reply	other threads:[~2012-05-29  9:45 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 [this message]
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=4FC499C4.8000904@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