[Qemu-devel] How does 'make test' work?

[Qemu-devel] How does 'make test' work?

[Alex Bligh]

How is one meant to make the tests? make test fails with:

make[1]: Entering directory `/home/amb/qemu/git/qemu/tests/tcg'
cc -m32 -I/home/amb/qemu/git/qemu/tcg -I/home/amb/qemu/git/qemu/tcg/i386 
-I/home/amb/qemu/git/qemu/linux-headers 
-I/home/amb/qemu/git/qemu/linux-headers -I. -I/home/amb/qemu/git/qemu 
-I/home/amb/qemu/git/qemu/include -I. -I. -I../.. -pthread 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include   -O2 
-g  -c -o test_path.o test_path.c
test_path.c:4:17: fatal error: iov.c: No such file or directory

If I fudge the include path it still doesn't work (see below).

I get the feeling I must have missed something.

Alex



amb@nimrod-ubuntu:~/qemu/git/qemu$ make test CFLAGS='-O2 -g 
-I/home/amb/qemu/git/qemu/util'
	CHK version_gen.h
make -C tests/tcg test
make[1]: Entering directory `/home/amb/qemu/git/qemu/tests/tcg'
cc -m32 -I/home/amb/qemu/git/qemu/tcg -I/home/amb/qemu/git/qemu/tcg/i386 
-I/home/amb/qemu/git/qemu/linux-headers 
-I/home/amb/qemu/git/qemu/linux-headers -I. -I/home/amb/qemu/git/qemu 
-I/home/amb/qemu/git/qemu/include -I. -I. -I../.. -pthread 
-I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include   -O2 
-g -I/home/amb/qemu/git/qemu/util -c -o test_path.o test_path.c
In file included from /home/amb/qemu/git/qemu/util/cutils.c:25:0,
                 from test_path.c:5:
/home/amb/qemu/git/qemu/include/qemu/host-utils.h: In function ‘mulu64’:
/home/amb/qemu/git/qemu/include/qemu/host-utils.h:35:5: error: unknown type 
name ‘__uint128_t’
/home/amb/qemu/git/qemu/include/qemu/host-utils.h:35:22: error: 
‘__uint128_t’ undeclared (first use in this function)
/home/amb/qemu/git/qemu/include/qemu/host-utils.h:35:22: note: each 
undeclared identifier is reported only once for each function it appears in
/home/amb/qemu/git/qemu/include/qemu/host-utils.h:35:34: error: expected 
‘,’ or ‘;’ before ‘a’
/home/amb/qemu/git/qemu/include/qemu/host-utils.h:37:5: warning: right 
shift count >= width of type [enabled by default]
/home/amb/qemu/git/qemu/include/qemu/host-utils.h: In function ‘muls64’:
/home/amb/qemu/git/qemu/include/qemu/host-utils.h:43:5: error: unknown type 
name ‘__int128_t’
/home/amb/qemu/git/qemu/include/qemu/host-utils.h:43:21: error: 
‘__int128_t’ undeclared (first use in this function)
/home/amb/qemu/git/qemu/include/qemu/host-utils.h:43:32: error: expected 
‘,’ or ‘;’ before ‘a’
/home/amb/qemu/git/qemu/include/qemu/host-utils.h:45:5: warning: right 
shift count >= width of type [enabled by default]
test_path.c: At top level:
test_path.c:7:19: fatal error: trace.c: No such file or directory
compilation terminated.
make[1]: *** [test_path.o] Error 1
make[1]: Leaving directory `/home/amb/qemu/git/qemu/tests/tcg'
make: *** [test] Error 2

-- 
Alex Bligh

Re: [Qemu-devel] How does 'make test' work?

[Laszlo Ersek]

On 06/29/13 19:51, Alex Bligh wrote:
> How is one meant to make the tests? make test fails with:
> 
> make[1]: Entering directory `/home/amb/qemu/git/qemu/tests/tcg'
> cc -m32 -I/home/amb/qemu/git/qemu/tcg -I/home/amb/qemu/git/qemu/tcg/i386
> -I/home/amb/qemu/git/qemu/linux-headers
> -I/home/amb/qemu/git/qemu/linux-headers -I. -I/home/amb/qemu/git/qemu
> -I/home/amb/qemu/git/qemu/include -I. -I. -I../.. -pthread
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include  
> -O2 -g  -c -o test_path.o test_path.c
> test_path.c:4:17: fatal error: iov.c: No such file or directory
> 
> If I fudge the include path it still doesn't work (see below).
> 
> I get the feeling I must have missed something.

See msg of commit f62cb1b6ddc2c82694abac23ab5eeddd85800074 I guess
(found with "git log -- tests/tcg/test_path.c").

Laszlo

Re: [Qemu-devel] How does 'make test' work?

[Peter Maydell]

On 29 June 2013 18:51, Alex Bligh <alex@alex.org.uk> wrote:
> How is one meant to make the tests? make test fails with:

"make check" is the target people actually run. It looks like
Paolo's file rearrangement broke the test_path test (since
it directly #includes other QEMU files) and nobody's noticed.

We should probably fix this and get the 'test' target
integrated into 'check' somehow (a bit tricky since at least
some of the tests depend on your host architecture and/or
availability of a crosscompiler).

thanks
-- PMM