diff options
| author | Arnaldo Carvalho de Melo <[email protected]> | 2017-03-02 16:00:26 -0300 |
|---|---|---|
| committer | Arnaldo Carvalho de Melo <[email protected]> | 2017-03-03 19:07:19 -0300 |
| commit | c8c188679ccfc86d9c7bac57ecf4b8205a061a06 (patch) | |
| tree | 3f665b2ebb5e1cb712b934a1106b40be72a8b371 /tools/perf/scripts/python | |
| parent | a0f213e14bb5cf4f190809b5811e1292bd614899 (diff) | |
tools build: Use the same CC for feature detection and actual build
When build with: 'make CC=clang' we were not using that CC to do
feature detection, which resulted in features being detected with gcc
and then the actual tools being built with clang.
Most of the time these compilers are compatible enough, so no
problem was being noticed.
As soon as a system with an old enough clang, one that hasn't
the cpuid.h header is used, and a gcc with it, the "get_cpuid" feature
will be found available but then code that will use can't be compiled.
Noticed with this combination:
/ $ gcc --version | head -1
gcc (Alpine 6.3.0) 6.3.0
/ $ clang --version | head -1
clang version 3.8.1 (tags/RELEASE_381/final)
/ $ cat /etc/alpine-release
3.5.0
/ $
Cc: Adrian Hunter <[email protected]>
Cc: David Ahern <[email protected]>
Cc: Jiri Olsa <[email protected]>
Cc: Namhyung Kim <[email protected]>
Cc: Wang Nan <[email protected]>
Link: http://lkml.kernel.org/n/[email protected]
Signed-off-by: Arnaldo Carvalho de Melo <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions