Re: [PATCH 0/3] Package Updates

Re: [PATCH 0/3] Package Updates

[Burton, Ross]

Hi,

First, sorry for the thread breaking, I've just joined this list and I
didn't get this mail.

Koen Kooi wrote:
>>  dbus: Update to version 1.5.12
>
> First: how was this tested?
> Second: From the dbus website:
>
>        The current stable branch is D-Bus 1.4.x. This is the recommended
> version for most purposes.
>        The current development branch is D-Bus 1.5.x, which will lead to a
> 1.6.x stable branch in future.
>
> Why are you deleting the stable branch based recipe and add one from
> the development branch?

The definition of stable and unstable in DBus isn't as hard and fast
as you'd really like -- the 1.5.x cycle is very slow and mostly stable
from a crashy point of view.

I'd say there is a good rationale for having both 1.4.x (.20, so that
also needs an upgrade) and 1.5.x in oe-core.  The default should be
1.4 for obvious reasons (it's the stable release), and 1.5 should be
there for people who need the improvements.  In particular there has
been a lot of work on performance, so anyone heavily using dbus (i.e.
anything using Telepathy, which is where the improvements came from)
should look at 1.5 because it will give a noticeable improvement on
slower hardware.

Ross

Re: [PATCH 0/3] Package Updates

[Radu Moisan]

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



On 05/28/2012 01:55 PM, Burton, Ross wrote:
> Hi,
>
> First, sorry for the thread breaking, I've just joined this list and I
> didn't get this mail.
>
> Koen Kooi wrote:
>>>   dbus: Update to version 1.5.12
>> First: how was this tested?
the only testing I've done so far is to ensure it build and then check 
the version with dbus-daemon --version
>> Second: From the dbus website:
>>
>>         The current stable branch is D-Bus 1.4.x. This is the recommended
>> version for most purposes.
>>         The current development branch is D-Bus 1.5.x, which will lead to a
>> 1.6.x stable branch in future.
>>
>> Why are you deleting the stable branch based recipe and add one from
>> the development branch?
> The definition of stable and unstable in DBus isn't as hard and fast
> as you'd really like -- the 1.5.x cycle is very slow and mostly stable
> from a crashy point of view.
>
> I'd say there is a good rationale for having both 1.4.x (.20, so that
> also needs an upgrade) and 1.5.x in oe-core.  The default should be
> 1.4 for obvious reasons (it's the stable release), and 1.5 should be
> there for people who need the improvements.  In particular there has
> been a lot of work on performance, so anyone heavily using dbus (i.e.
> anything using Telepathy, which is where the improvements came from)
> should look at 1.5 because it will give a noticeable improvement on
> slower hardware.
>
> Ross
I suppose, then, I should add another recipe and support both. However, 
can someone point out how can I make one of them default.
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

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

Re: [PATCH 0/3] Package Updates

[Andrei Gherzan]

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

On 05/28/2012 02:21 PM, Radu Moisan wrote:
>
>
> On 05/28/2012 01:55 PM, Burton, Ross wrote:
>> Hi,
>>
>> First, sorry for the thread breaking, I've just joined this list and I
>> didn't get this mail.
>>
>> Koen Kooi wrote:
>>>>   dbus: Update to version 1.5.12
>>> First: how was this tested?
> the only testing I've done so far is to ensure it build and then check 
> the version with dbus-daemon --version

Dbus comes with a test suite. Running those should be a must.
>>> Second: From the dbus website:
>>>
>>>         The current stable branch is D-Bus 1.4.x. This is the recommended
>>> version for most purposes.
>>>         The current development branch is D-Bus 1.5.x, which will lead to a
>>> 1.6.x stable branch in future.
>>>
>>> Why are you deleting the stable branch based recipe and add one from
>>> the development branch?
>> The definition of stable and unstable in DBus isn't as hard and fast
>> as you'd really like -- the 1.5.x cycle is very slow and mostly stable
>> from a crashy point of view.
>>
>> I'd say there is a good rationale for having both 1.4.x (.20, so that
>> also needs an upgrade) and 1.5.x in oe-core.  The default should be
>> 1.4 for obvious reasons (it's the stable release), and 1.5 should be
>> there for people who need the improvements.  In particular there has
>> been a lot of work on performance, so anyone heavily using dbus (i.e.
>> anything using Telepathy, which is where the improvements came from)
>> should look at 1.5 because it will give a noticeable improvement on
>> slower hardware.
>>
>> Ross
> I suppose, then, I should add another recipe and support both. 
> However, can someone point out how can I make one of them default.

DEFAULT_PREFERENCE

@g

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

Re: [PATCH 0/3] Package Updates

[Paul Eggleton]

On Monday 28 May 2012 14:21:30 Andrei Gherzan wrote:
> On 05/28/2012 02:21 PM, Radu Moisan wrote:
> > I suppose, then, I should add another recipe and support both.
> > However, can someone point out how can I make one of them default.
> 
> DEFAULT_PREFERENCE

i.e. set DEFAULT_PREFERENCE = "-1" in the newer recipe.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre

Re: [PATCH 0/3] Package Updates

[Radu Moisan]

On 05/28/2012 02:21 PM, Andrei Gherzan wrote:
> Dbus comes with a test suite. Running those should be a must.
I could not find how to run the test suite. I've tried dbus-daemon, 
dbus-monitor, and the rest, but non of them have options for some 
runtime checks. Other than that I imagine the test suite you mention 
must come in a separate package. Do we have a recipe for that to? Which 
image should I build to have that package included and be able to test?

Radu

Re: [PATCH 0/3] Package Updates

[Andrei Gherzan]

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

On Mon, May 28, 2012 at 4:24 PM, Radu Moisan <radu.moisan@intel.com> wrote:

> On 05/28/2012 02:21 PM, Andrei Gherzan wrote:
>
>> Dbus comes with a test suite. Running those should be a must.
>>
> I could not find how to run the test suite. I've tried dbus-daemon,
> dbus-monitor, and the rest, but non of them have options for some runtime
> checks. Other than that I imagine the test suite you mention must come in a
> separate package. Do we have a recipe for that to? Which image should I
> build to have that package included and be able to test?
>
>
There is an internal test suite for dbus. You can enable building those
tests in configure:
"--enable-tests"

@g

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

Re: [PATCH 0/3] Package Updates

[Burton, Ross]

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?

Ross

Re: [PATCH 0/3] Package Updates

[Richard Purdie]

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

Re: [PATCH 0/3] Package Updates

[Burton, Ross]

On 28 May 2012 14:44, Richard Purdie <richard.purdie@linuxfoundation.org> wrote:
>> 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.

I guess the overhead of setting up a qemu just to run the tests is a
bit excessive. :)

Ross

Re: [PATCH 0/3] Package Updates

[Andrei Gherzan]

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

On Mon, May 28, 2012 at 4:44 PM, Richard Purdie <
richard.purdie@linuxfoundation.org> 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.
>
>
The fact that these tests are not compiled by default it's good. As a
normal user of dbus i don't need those. But while doing an update a compile
with tests i think it's necessary.

@g

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

Re: [PATCH 0/3] Package Updates

[Philip Balister]

On 05/28/2012 09:58 AM, Andrei Gherzan wrote:
> On Mon, May 28, 2012 at 4:44 PM, Richard Purdie <
> richard.purdie@linuxfoundation.org> 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.
>>
>>
> The fact that these tests are not compiled by default it's good. As a
> normal user of dbus i don't need those. But while doing an update a compile
> with tests i think it's necessary.

Can you build the tests and package them separately? Then they could be
installed as part of a test image.

Philip

Re: [PATCH 0/3] Package Updates

[Radu Moisan]

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



On 05/29/2012 03:10 PM, Philip Balister wrote:
> On 05/28/2012 09:58 AM, Andrei Gherzan wrote:
>> On Mon, May 28, 2012 at 4:44 PM, Richard Purdie<
>> richard.purdie@linuxfoundation.org>  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.
>>>
>>>
>> The fact that these tests are not compiled by default it's good. As a
>> normal user of dbus i don't need those. But while doing an update a compile
>> with tests i think it's necessary.
> Can you build the tests and package them separately? Then they could be
> installed as part of a test image.
>
> Philip
>
That would certainly be an option, but I really don't know where to 
start from :)
Meanwhile, I tried to further debug my scenario with 
--enable-modular-tests and I tried to manually resolve the missing *.h 
files (by copying them from dbus-glib to dbus include folder) just to 
see where is goes. I found out, somehow expected, that further undefined 
reference errors were thrown (to functions from dbus-glib). Thus now I'm 
looking to point somehow dbus tests to link against dbus-glib. Does 
anyone have a clue where should I look?

Radu

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

dbus test suite

[Radu Moisan]

[-- 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 --]

Re: dbus test suite

[Radu Moisan]

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



On 05/29/2012 11:29 AM, Radu Moisan wrote:
>
>
> 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
>
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" && ln -s "../libdbus-testutils.la" 
"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
| compilation terminated.
| make[3]: *** [test_corrupt-corrupt.o] Error 1
| make[3]: Leaving directory 
`/home/radu/Documents/Development/yocto/build/tmp/work/i586-poky-linux/dbus-1.4.20-r3.0/dbus-1.4.20/test'
| make[2]: *** [all-recursive] Error 1
| make[2]: Leaving directory 
`/home/radu/Documents/Development/yocto/build/tmp/work/i586-poky-linux/dbus-1.4.20-r3.0/dbus-1.4.20/test'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory 
`/home/radu/Documents/Development/yocto/build/tmp/work/i586-poky-linux/dbus-1.4.20-r3.0/dbus-1.4.20'
| make: *** [all] Error 2
| ERROR: oe_runmake failed
NOTE: package dbus-1.4.20-r3.0: task do_compile: Failed
ERROR: Task 7 
(/home/radu/Documents/Development/yocto/poky/meta/recipes-core/dbus/dbus_1.4.20.bb, 
do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1120 tasks of which 1119 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_compile
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

Radu

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

Re: dbus test suite

[Andrei Gherzan]

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

On Tue, May 29, 2012 at 12:23 PM, Radu Moisan <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" && ln -s "../libdbus-testutils.la" "
> 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

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

Re: dbus test suite

[Radu Moisan]

[-- 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 --]

Re: dbus test suite

[Florin Sarbu]

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

On 05/29/2012 12:41 PM, Radu Moisan wrote:
>
> 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).
>
that would be dbus-glib you need at this point as Andrei pointed out, 
not python-dbus
> Radu
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core


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

Re: dbus test suite

[Radu Moisan]

[-- 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 --]

Re: [PATCH 0/3] Package Updates

[Radu Moisan]

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



On 05/28/2012 04:26 PM, Andrei Gherzan wrote:
> On Mon, May 28, 2012 at 4:24 PM, Radu Moisan <radu.moisan@intel.com 
> <mailto:radu.moisan@intel.com>> wrote:
>
>     On 05/28/2012 02:21 PM, Andrei Gherzan wrote:
>
>         Dbus comes with a test suite. Running those should be a must.
>
>     I could not find how to run the test suite. I've tried
>     dbus-daemon, dbus-monitor, and the rest, but non of them have
>     options for some runtime checks. Other than that I imagine the
>     test suite you mention must come in a separate package. Do we have
>     a recipe for that to? Which image should I build to have that
>     package included and be able to test?
>
>
> There is an internal test suite for dbus. You can enable building 
> those tests in configure:
> "--enable-tests"
>
> @g
>
So, isn't there a way of specifying build options in some file that 
bitbake will use afterwards to do the build? For instance where from 
./configure is executed (from within bitbake I assume). I tried to take 
a look over configure file of dbus but could not figure out a way of 
hardcoding the --enable-tests option (not that hardcoding would be a 
best choice, but for testing purposes I considered it a choice). Any 
info on this is much appreciated.

Thanks,
Radu

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

Re: [PATCH 0/3] Package Updates

[Radu Moisan]

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



On 05/29/2012 09:28 AM, Radu Moisan wrote:
>
>
> On 05/28/2012 04:26 PM, Andrei Gherzan wrote:
>> On Mon, May 28, 2012 at 4:24 PM, Radu Moisan <radu.moisan@intel.com 
>> <mailto:radu.moisan@intel.com>> wrote:
>>
>>     On 05/28/2012 02:21 PM, Andrei Gherzan wrote:
>>
>>         Dbus comes with a test suite. Running those should be a must.
>>
>>     I could not find how to run the test suite. I've tried
>>     dbus-daemon, dbus-monitor, and the rest, but non of them have
>>     options for some runtime checks. Other than that I imagine the
>>     test suite you mention must come in a separate package. Do we
>>     have a recipe for that to? Which image should I build to have
>>     that package included and be able to test?
>>
>>
>> There is an internal test suite for dbus. You can enable building 
>> those tests in configure:
>> "--enable-tests"
>>
>> @g
>>
> So, isn't there a way of specifying build options in some file that 
> bitbake will use afterwards to do the build? For instance where from 
> ./configure is executed (from within bitbake I assume). I tried to 
> take a look over configure file of dbus but could not figure out a way 
> of hardcoding the --enable-tests option (not that hardcoding would be 
> a best choice, but for testing purposes I considered it a choice). Any 
> info on this is much appreciated.
>
> Thanks,
> Radu
Found it in oe_runconf(). Will try to build them, see what comes out of 
it :)
Any comments still apreciated.

Radu

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