diff options
| author | Marcin Slusarz <marcin.slusarz@gmail.com> | 2013-02-17 16:03:36 +0100 |
|---|---|---|
| committer | Arnaldo Carvalho de Melo <acme@redhat.com> | 2013-03-13 20:57:27 +0100 |
| commit | d2f32479e5526a1ab3b4e43910fcb279871524ce (patch) | |
| tree | 39c0d91b56d7d783b7b8118c8a246a6c291e90a0 /tools/perf/CREDITS | |
| parent | perf report: Fix build with NO_NEWT=1 (diff) | |
| download | linux-d2f32479e5526a1ab3b4e43910fcb279871524ce.tar.xz linux-d2f32479e5526a1ab3b4e43910fcb279871524ce.zip | |
perf tools: check if -DFORTIFY_SOURCE=2 is allowed
It seems gcc (4.7.2) defines _FORTIFY_SOURCE internally and becomes
confused when it sees another definition in flags.
For me, build failed like this:
CHK glibc
Makefile:548: *** No gnu/libc-version.h found, please install glibc-dev[el]/glibc-static. Stop.
and only with V=1 it printed:
<command-line>:0:0: error: "_FORTIFY_SOURCE" redefined [-Werror]
<stdin>:1:0: note: this is the location of the previous definition
Signed-off-by: Marcin Slusarz <marcin.slusarz@gmail.com>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: Paul Mackerras <paulus@samba.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/1361113416-8662-1-git-send-email-marcin.slusarz@gmail.com
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
Diffstat (limited to 'tools/perf/CREDITS')
0 files changed, 0 insertions, 0 deletions