137 test failures ?

137 test failures ?

[Dennis Clarke]

After a clean build I see "make check" reports :


                 === libffi Summary ===

# of unexpected failures        137
# of unresolved testcases       137


This is almost certainly because the test process ignores the CFLAGS and 
performs all tests using the wrong linkage options etc and we get total 
failure.

Where in the test process can I see the CFLAGS being used and can I run 
the tests entirely manually one at a time myself ?

Also, system is Solaris 10 using the Oracle Studio 12.4 compiler set.

Dennis

Re: 137 test failures ?

[Dennis Clarke]

> Also, system is Solaris 10 using the Oracle Studio 12.4 compiler set.


As a follow up, to myself, I can easily compile and link anything in the 
testsuite and run manually provided that the correct $CFLAGS are used 
thus :

$ pwd
/usr/local/build/libffi-3.2.1_SunOS5.10_sparcv9.002

$ $CC $CFLAGS 
-I/usr/local/build/libffi-3.2.1_SunOS5.10_sparcv9.002/sparc-sun-solaris2.10 
\
 > -I 
/usr/local/build/libffi-3.2.1_SunOS5.10_sparcv9.002/sparc-sun-solaris2.10/include 
\
 > -c -o /tmp/closure_fn0.o ./testsuite/libffi.call/closure_fn0.c

$ $CC $CFLAGS -R `pwd`/sparc-sun-solaris2.10/.libs -L 
`pwd`/sparc-sun-solaris2.10/.libs -o /tmp/closure_fn0 /tmp/closure_fn0.o 
-lffi
$

$ file /tmp/closure_fn0
/tmp/closure_fn0: ELF 64-bit MSB executable, SPARC V9, total store 
ordering, version 1, dynamically linked (uses shared libs), not stripped

$ /tmp/closure_fn0
1 2 3 4 127 429 7 8 9 10 11 12 13 19 21 1 3: 680
res: 680

So the real question is, what are the expected results from every test 
and then I can run them all manually.

Dennis