https://bugs.kde.org/show_bug.cgi?id=445300
--- Comment #9 from Paul Floyd <pjfl...@wanadoo.fr> --- > I can do that, but to save us both some time, is there a list of things I > should be making sure are installed before I run the tests? I didn't know I > needed gdb, for example. At least you will need gsed and gdb. No harm installing coreutils as well. You'll need to run autogen and configure again. The gdbserver_tests should contain a symlink to gdb. 'make check' and 'make regtest' should run a script to make this link. If that does not work you can run gdbserver_tests/make_local_links /path/to//gdb My latest FreeBSD tests were == 745 tests, 12 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == memcheck/tests/amd64/insn-pmovmskb (stderr) memcheck/tests/clientperm (stderr) memcheck/tests/gone_abrt_xml (stderr) memcheck/tests/origin5-bz2 (stderr) memcheck/tests/varinfo2 (stderr) memcheck/tests/varinfo5 (stderr) memcheck/tests/varinfo6 (stderr) helgrind/tests/tls_threads (stderr) drd/tests/atomic_var (stderr) drd/tests/omp_matinv (stderr) drd/tests/omp_matinv_racy (stderr) drd/tests/omp_prime_racy (stderr) I have noticed that a small number of tests depend on the type of install (e.g., one depends on the filesystem in use). -- You are receiving this mail because: You are watching all bug changes.
