Ian Rogers 13e07691a1 tools/resolve_btfids: Alter how HOSTCC is forced ... HOSTCC is always wanted when building. Setting CC to HOSTCC happens after tools/scripts/Makefile.include is included, meaning flags are set assuming say CC is gcc, but then it can be later set to HOSTCC which may be clang. tools/scripts/Makefile.include is needed for host set up and common macros in objtool's Makefile. Rather than override CC to HOSTCC, just pass CC as HOSTCC to Makefile.build, the libsubcmd builds and the linkage step. This means the Makefiles don't see things like CC changing and tool flag determination, and similar, work properly. Also, clear the passed subdir as otherwise an outer build may break by inadvertently passing an inappropriate value. Signed-off-by: Ian Rogers <irogers@google.com> Signed-off-by: Daniel Borkmann <daniel@iogearbox.net> Acked-by: Jiri Olsa <jolsa@kernel.org> Link: https://lore.kernel.org/bpf/20230124064324.672022-2-irogers@google.com		2023-01-25 18:28:14 +01:00
..
bpftool	bpftool: Always disable stack protection for BPF objects	2023-01-13 16:44:21 +01:00
resolve_btfids	tools/resolve_btfids: Alter how HOSTCC is forced	2023-01-25 18:28:14 +01:00
runqslower	tools: runqslower: Build and use lightweight bootstrap version of bpftool	2022-07-15 12:01:30 -07:00
.gitignore
bpf_asm.c
bpf_dbg.c
bpf_exp.l
bpf_exp.y
bpf_jit_disasm.c	tools bpf_jit_disasm: Fix compilation error with new binutils	2022-08-01 15:30:48 -03:00
Makefile	tools bpf_jit_disasm: Don't display disassembler-four-args feature test	2022-08-01 15:31:51 -03:00