Page 1 of 1

[SOLVED] make check fails

Posted: Thu Dec 27, 2012 12:53 pm
by alberich
Hello,
on both versions, the nightly and 3.0.0-betaR4215 (with installer and then manually recompiling), mak check fails with the same message (below).
Any ideas?
al

Code: Select all

cs_file_test.c: In function ‘_create_test_data’:
cs_file_test.c:79:20: warning: passing argument 4 of ‘cs_file_open’ from incompatible pointer type [enabled by default]
../src/base/cs_file.h:152:1: note: expected ‘MPI_Info’ but argument is of type ‘MPI_Comm’
cs_file_test.c:79:20: error: too few arguments to function ‘cs_file_open’
../src/base/cs_file.h:152:1: note: declared here
cs_file_test.c: In function ‘main’:
cs_file_test.c:120:25: error: ‘CS_FILE_NO_MPI_IO’ undeclared (first use in this function)
cs_file_test.c:120:25: note: each undeclared identifier is reported only once for each function it appears in
cs_file_test.c:121:25: error: ‘CS_FILE_EXPLICIT_OFFSETS’ undeclared (first use in this function)
cs_file_test.c:122:25: error: ‘CS_FILE_INDIVIDUAL_POINTERS’ undeclared (first use in this function)
cs_file_test.c:189:22: warning: passing argument 4 of ‘cs_file_open’ from incompatible pointer type [enabled by default]
../src/base/cs_file.h:152:1: note: expected ‘MPI_Info’ but argument is of type ‘struct ompi_communicator_t *’
cs_file_test.c:189:22: error: too few arguments to function ‘cs_file_open’
../src/base/cs_file.h:152:1: note: declared here
cs_file_test.c:302:22: warning: passing argument 4 of ‘cs_file_open’ from incompatible pointer type [enabled by default]
../src/base/cs_file.h:152:1: note: expected ‘MPI_Info’ but argument is of type ‘struct ompi_communicator_t *’
cs_file_test.c:302:22: error: too few arguments to function ‘cs_file_open’
../src/base/cs_file.h:152:1: note: declared here
make[2]: *** [cs_file_test.o] Error 1
[/size]

Re: make check fails

Posted: Thu Dec 27, 2012 2:33 pm
by Yvan Fournier
Hello,

"make check" is not used much (it does not include validation/install checks, but mainly very low-level unit tests, requiring human interpretation), so it might not be fully up to date.

I'll fix it for the next releases, but in the meantime, just ignore that failure.

Regards,

Yvan