Hi Simon, > > * Linux/x86_64 > > > > 8 of 8 tests failed > > > > The reason is that I have valgrind 3.5.0 installed, and "make check" > > apparently > > runs valgrind on many 'bash' processes, each leading to a failure. See > > attached > > log. > > Can you try and run this for me on that system: > > valgrind -q --error-exitcode=1 --leak-check=no /bin/bash -c 'exit 0' > echo $?
It prints a lot of output to stderr and terminates with exit code 1. > Currently valgrind-tests checks whether running 'valgrind -q true' > works, and then enables valgrind. I'm considering changing > valgrind-tests.m4 into testing that 'valgrind $SHELL -c "exit 0"' works. Yes. This should be necessary only if libtool has produced wrapper scripts for the executables. Cf. function func_ltwrapper_executable_p in ltmain.sh. Bruno -- In memoriam Alexander Litvinenko <http://en.wikipedia.org/wiki/Alexander_Litvinenko>
