hm, probably one of these commits:
8a0c4c2843d3 perf tools: Fix libunwind build and feature detection for 32-bit
build
28e962b9d79f perf tools: Fix 32-bit cross build
74af377bc25d perf tools: Fix non-debug build
9402802a416c perf tools: Fix test_on_exit for 32-bit build
broke the suppression of the auto-detection messages on repeat invocations
of 'make', if all testcases pass.
'make' used to display this on repeat invocations:
comet:~/tip/tools/perf> make
BUILD: Doing 'make -j12' parallel build
comet:~/tip/tools/perf> make
BUILD: Doing 'make -j12' parallel build
comet:~/tip/tools/perf> make
BUILD: Doing 'make -j12' parallel build
Now it displays the spammy auto-detection all the time:
comet:~/tip/tools/perf> make
BUILD: Doing 'make -j12' parallel build
Auto-detecting system features:
... backtrace: [ on ]
... dwarf: [ on ]
... fortify-source: [ on ]
... glibc: [ on ]
... gtk2: [ on ]
... gtk2-infobar: [ on ]
... libaudit: [ on ]
... libbfd: [ on ]
... libelf: [ on ]
... libelf-getphdrnum: [ on ]
... libelf-mmap: [ on ]
... libnuma: [ on ]
... libperl: [ on ]
... libpython: [ on ]
... libpython-version: [ on ]
... libslang: [ on ]
... libunwind: [ on ]
... on-exit: [ on ]
... stackprotector: [ on ]
... stackprotector-all: [ on ]
maybe a new testcase fails on my box, but is not properly displayed?
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
