Changes in Makefile

293f324c - tools: Unify top-level quiet infrastructure

Thu, 13 Feb 2025 21:06:21 +0000

tools: Unify top-level quiet infrastructureCommit f2868b1a66d4f40f ("perf tools: Expose quiet/verbose variables inMakefile.perf") moved the quiet infrastructure out oftools/build/Makefile.build and into the top-level Makefile.perf file sothat the quiet infrastructure could be used throughout perf and not justin Makefile.build.Extract out the quiet infrastructure into Makefile.include so that itcan be leveraged outside of perf.Fixes: f2868b1a66d4f40f ("perf tools: Expose quiet/verbose variables in Makefile.perf")Reviewed-by: Jiri Olsa Signed-off-by: Charlie Jenkins Acked-by: Andrii Nakryiko Cc: Adrian Hunter Cc: Alexander Shishkin Cc: Alexei Starovoitov Cc: Benjamin Tissoires Cc: Daniel Borkmann Cc: Daniel Lezcano Cc: Eduard Zingerman Cc: Hao Luo Cc: Ian Rogers Cc: Ingo Molnar Cc: Jiri Kosina Cc: John Fastabend Cc: Josh Poimboeuf Cc: KP Singh Cc: Lukasz Luba Cc: Mark Rutland Cc: Martin KaFai Lau Cc: Mykola Lysenko Cc: Namhyung Kim Cc: Peter Zijlstra Cc: Quentin Monnet Cc: Rafael J. Wysocki Cc: Shuah Khan Cc: Song Liu Cc: Stanislav Fomichev Cc: Steven Rostedt (VMware) Cc: Yonghong Song Cc: Zhang Rui Link: https://lore.kernel.org/r/20250213-quiet_tools-v3-1-07de4482a581@rivosinc.comSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/build/Makefile

b53f20b3 - tools build: Provide consistent build options for fixdep

Thu, 15 Aug 2024 07:20:46 +0000

tools build: Provide consistent build options for fixdepThe fixdep binary is being compiled and linked in one step. While thehost linker flags are passed to the compiler the host compiler flags aremissed.That leads to build errors at least on x86_64, arm64 and s390 as resultof the compiler vs linker flags inconsistency. For example, during RPMpackage build redhat-hardened-ld script is provided to gcc, whileredhat-hardened-cc1 script is missed.Provide both KBUILD_HOSTCFLAGS and KBUILD_HOSTLDFLAGS to avoid that.Fixes: ea974028a049f2ce ("tools build: Avoid circular .fixdep-in.o.cmd issues")Closes: https://lore.kernel.org/lkml/99ae0d34-ed76-4ca0-a9fd-c337da33c9f9@leemhuis.info/Reported-by: Thorsten Leemhuis Reviewed-by: Brian Norris Signed-off-by: Alexander Gordeev Tested-by: Thorsten Leemhuis Acked-by: Jiri Olsa Link: https://lore.kernel.org/r/20240815072046.1002837-1-agordeev@linux.ibm.comSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/build/Makefile

ea974028 - tools build: Avoid circular .fixdep-in.o.cmd issues

Mon, 15 Jul 2024 20:32:43 +0000

tools build: Avoid circular .fixdep-in.o.cmd issuesThe 'fixdep' tool is used to post-process dependency files for variousreasons, and it runs after every object file generation command. Thiseven includes 'fixdep' itself.In Kbuild, this isn't actually a problem, because it uses a singlecommand to generate fixdep (a compile-and-link command on fixdep.c), andafterward runs the fixdep command on the accompanying .fixdep.cmd file.In tools/ builds (which notably is maintained separately from Kbuild),fixdep is generated in several phases: 1. fixdep.c -> fixdep-in.o 2. fixdep-in.o -> fixdepThus, fixdep is not available in the post-processing for step 1, andinstead, we generate .cmd files that look like: ## from tools/objtool/libsubcmd/.fixdep.o.cmd # cannot find fixdep (/path/to/linux/tools/objtool/libsubcmd//fixdep) [...]These invalid .cmd files are benign in some respects, but cause problemsin others (such as the linked reports).Because the tools/ build system is rather complicated in its own right(and pointedly different than Kbuild), I choose to simply open-code therule for building fixdep, and avoid the recursive-make indirection thatproduces the problem in the first place.Signed-off-by: Brian Norris Acked-by: Jiri Olsa Cc: Ian Rogers Cc: Josh Poimboeuf Cc: Masahiro Yamada Cc: Namhyung Kim Cc: Peter Zijlstra Cc: Thomas Richter Link: https://lore.kernel.org/all/Zk-C5Eg84yt6_nml@google.com/Link: https://lore.kernel.org/r/20240715203325.3832977-3-briannorris@chromium.orgSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/build/Makefile

5c816641 - kbuild: replace $(if A,A,B) with $(or A,B)

Fri, 11 Feb 2022 05:14:11 +0000

kbuild: replace $(if A,A,B) with $(or A,B)$(or ...) is available since GNU Make 3.81, and useful to shorten thecode in some places.Covert as follows: $(if A,A,B) --> $(or A,B)This patch also converts: $(if A, A, B) --> $(or A, B)Strictly speaking, the latter is not an equivalent conversion becauseGNU Make keeps spaces after commas; if A is not empty, $(if A, A, B)expands to " A", while $(or A, B) expands to "A".Anyway, preceding spaces are not significant in the code hunks I touched.Signed-off-by: Masahiro Yamada Reviewed-by: Nicolas Schier List of files: /linux-6.15/tools/build/Makefile

8af52e69 - tools build: Fix feature detect clean for out of source builds

Mon, 16 Aug 2021 13:07:05 +0000

tools build: Fix feature detect clean for out of source buildsCurrently the clean target when using O= isn't cleaning the featuredetect output. This is because O= and OUTPUT= are set to canonicalpaths. For example in tools/perf/Makefile: FULL_O := $(shell cd $(PWD); readlink -f $(O) || echo $(O))This means that OUTPUT ends in a / and most usages prepend it to a filewithout adding an extra /. This line that was changed adds an extra /before the 'feature' folder but not to the end, resulting in a cleancommand like this: rm -f /tmp/build//featuretest-all.bin ...After the change the clean command looks like this: rm -f /tmp/build/feature/test-all.bin ...Fixes: 762323eb39a257c3 ("perf build: Move feature cleanup under tools/build")Signed-off-by: James Clark Acked-by: Jiri Olsa Link: http://lore.kernel.org/lkml/20210816130705.1331868-1-james.clark@arm.comSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/build/Makefile

762323eb - perf build: Move feature cleanup under tools/build

Wed, 24 Feb 2021 15:08:31 +0000

perf build: Move feature cleanup under tools/buildArnaldo reported issue for following build command: $ rm -rf /tmp/krava; mkdir /tmp/krava; make O=/tmp/krava clean CLEAN config /bin/sh: line 0: cd: /tmp/krava/feature/: No such file or directory ../../scripts/Makefile.include:17: *** output directory "/tmp/krava/feature/" does not exist. Stop. make[1]: *** [Makefile.perf:1010: config-clean] Error 2 make: *** [Makefile:90: clean] Error 2The problem is that now that we include scripts/Makefile.includein feature's Makefile (which is fine and needed), we need to ensurethe OUTPUT directory exists, before executing (out of tree) cleancommand.Removing the feature's cleanup from perf Makefile and fixingfeature's cleanup under build Makefile, so it now checks thatthere's existing OUTPUT directory before calling the clean.Fixes: 211a741cd3e1 ("tools: Factor Clang, LLC and LLVM utils definitions")Reported-by: Arnaldo Carvalho de Melo Signed-off-by: Jiri Olsa Tested-by: Arnaldo Carvalho de Melo Tested-by: Sedat Dilek # LLVM/Clang v13-gitCc: Alexander Shishkin Cc: Ian Rogers Cc: Mark Rutland Cc: Michael Petlan Cc: Namhyung Kim Cc: Peter Zijlstra Link: http://lore.kernel.org/lkml/20210224150831.409639-1-jolsa@kernel.orgSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/build/Makefile

c8a950d0 - tools: Factor HOSTCC, HOSTLD, HOSTAR definitions

Tue, 10 Nov 2020 16:43:05 +0000

tools: Factor HOSTCC, HOSTLD, HOSTAR definitionsSeveral Makefiles in tools/ need to define the host toolchain variables.Move their definition to tools/scripts/Makefile.includeSigned-off-by: Jean-Philippe Brucker Signed-off-by: Andrii Nakryiko Acked-by: Jiri Olsa Acked-by: Rafael J. Wysocki Link: https://lore.kernel.org/bpf/20201110164310.2600671-2-jean-philippe@linaro.org List of files: /linux-6.15/tools/build/Makefile

661b37cd - tools, bpf/build: Cleanup feature files on make clean

Thu, 27 Aug 2020 08:53:36 +0000

tools, bpf/build: Cleanup feature files on make cleanThe system for "Auto-detecting system features" located undertools/build/ are (currently) used by perf, libbpf and bpftool. It cancontain stalled feature detection files, which are not cleaned up bylibbpf and bpftool on make clean (side-note: perf tool is correct).Fix this by making the users invoke the make clean target.Some details about the changes. The libbpf Makefile already had aclean-config target (which seems to be copy-pasted from perf), but thistarget was not "connected" (a make dependency) to clean target. Choosenot to rename target as someone might be using it. Did change the outputfrom "CLEAN config" to "CLEAN feature-detect", to make it more clearwhat happens.This is related to the complaint and troubleshooting in the followinglink: https://lore.kernel.org/lkml/20200818122007.2d1cfe2d@carbon/Signed-off-by: Jesper Dangaard Brouer Signed-off-by: Daniel Borkmann Acked-by: Jiri Olsa Link: https://lore.kernel.org/lkml/20200818122007.2d1cfe2d@carbon/Link: https://lore.kernel.org/bpf/159851841661.1072907.13770213104521805592.stgit@firesoul List of files: /linux-6.15/tools/build/Makefile

b90a3680 - kbuild: Rename HOSTLDFLAGS to KBUILD_HOSTLDFLAGS

Tue, 10 Jul 2018 00:46:00 +0000

kbuild: Rename HOSTLDFLAGS to KBUILD_HOSTLDFLAGSIn preparation for enabling command line LDFLAGS, re-name HOSTLDFLAGSto KBUILD_HOSTLDFLAGS as the internal use only flags. This should nothave any visible effects.Signed-off-by: Laura Abbott Signed-off-by: Masahiro Yamada List of files: /linux-6.15/tools/build/Makefile

8b247a92 - tools: build: Use HOSTLDFLAGS with fixdep

Tue, 10 Jul 2018 00:45:57 +0000

tools: build: Use HOSTLDFLAGS with fixdepThe final link of fixdep uses LDFLAGS but not the existing HOSTLDFLAGS.Fix this.Signed-off-by: Laura Abbott Acked-by: Jiri Olsa Signed-off-by: Masahiro Yamada List of files: /linux-6.15/tools/build/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/tools/build/Makefile

85e0d509 - perf build: Add special fixdep cleaning rule

Fri, 17 Feb 2017 14:00:54 +0000

perf build: Add special fixdep cleaning ruleIngo reported following build failure:On Sat, Feb 11, 2017 at 12:12:34PM +0100, Ingo Molnar wrote:>> So I had this oldish 32-bit 15.10 Ubuntu installation around (fully updated), and> trying to build perf gave me:>> deimos:~/tip/tools/perf> make> BUILD: Doing 'make -j4' parallel build> make[3]: *** No rule to make target '/usr/include/x86_64-linux-gnu/sys/types.h', needed by 'fixdep.o'. Stop.> Makefile:42: recipe for target 'fixdep-in.o' failed> make[2]: *** [fixdep-in.o] Error 2> /home/mingo/tip/tools/build/Makefile.include:4: recipe for target 'fixdep' failed> make[1]: *** [fixdep] Error 2> Makefile:68: recipe for target 'all' failed> make: *** [all] Error 2>> Now this got a bit better after I did a 'make mrproper' in the kernel tree:>> deimos:~/tip/tools/perf> make> BUILD: Doing 'make -j4' parallel build> HOSTCC fixdep.o> /home/mingo/tip/tools/build/fixdep: 1: /home/mingo/tip/tools/build/fixdep: Syntax error: "(" unexpected> /home/mingo/tip/tools/build/Makefile.build:101: recipe for target 'fixdep.o' failed> make[3]: *** [fixdep.o] Error 2> Makefile:42: recipe for target 'fixdep-in.o' failed> make[2]: *** [fixdep-in.o] Error 2> /home/mingo/tip/tools/build/Makefile.include:4: recipe for target 'fixdep' failed> make[1]: *** [fixdep] Error 2> Makefile:68: recipe for target 'all' failed> make: *** [all] Error 2>> After some digging it turns out that my 'fixdep' binary was 64-bit:>> deimos:~/tip/tools/perf> file /home/mingo/tip/tools/build/fixdep> /home/mingo/tip/tools/build/fixdep: ELF 64-bit LSB executable, x86-64, version 1> (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux> 2.6.32, BuildID[sha1]=d527f736b57b5ba47210fbcb562a3b52867d21c1, not stripped>> But it did not get cleaned out by 'make clean'.>> Only after I did a 'make clean' in tools/ itself, did it get built properly.It shows we don't clean up properly the fixdep objects, so addingspecial rule for that.Signed-off-by: Jiri Olsa Reported-by: Ingo Molnar Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra Link: http://lkml.kernel.org/r/1487340058-10496-2-git-send-email-jolsa@kernel.orgSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/build/Makefile

e19b7cee - make use of make variable CURDIR instead of calling pwd

Tue, 22 Nov 2016 08:30:26 +0000

make use of make variable CURDIR instead of calling pwdmake already provides the current working directory in a variable, so makeuse of it instead of forking a shell. Also replace usage of PWD byCURDIR. PWD is provided by most shells, but not all, so this makes thebuild system more robust.Signed-off-by: Uwe Kleine-König Signed-off-by: Michal Marek List of files: /linux-6.15/tools/build/Makefile

6b3db6f9 - tools build: Make fixdep a hostprog

Tue, 27 Sep 2016 14:18:46 +0000

tools build: Make fixdep a hostprogIt is used in the build process, so stop suppressing its build in toolscross builds.Signed-off-by: Jiri Olsa Tested-by: Arnaldo Carvalho de Melo Cc: Andi Kleen Cc: Madhavan Srinivasan Cc: Peter Zijlstra Cc: Sukadev Bhattiprolu Cc: linuxppc-dev@lists.ozlabs.orgLink: http://lkml.kernel.org/r/20160927141846.GA6589@krava[ Use HOSTCC on the $(OUTPUT)fixdep target, it was using the x-compiler to link fixdep-in.o, that was correctly built with HOSTCC and thus failing ]Signed-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/build/Makefile

0c3b7e42 - tools build: Add support for host programs format

Tue, 27 Sep 2016 14:18:46 +0000

tools build: Add support for host programs formatIn some cases, like for fixdep and shortly for jevents, we need to build a toolto run on the host that will be used in building a tool, such as perf, that isbeing cross compiled, so do like the kernel and provide HOSTCC, HOSTLD and HOSTARto do that.Signed-off-by: Jiri Olsa Requested-by: Andi Kleen Requested-and-Tested-by: Arnaldo Carvalho de Melo Cc: Madhavan Srinivasan Cc: Peter Zijlstra Cc: Sukadev Bhattiprolu Cc: linuxppc-dev@lists.ozlabs.orgLink: http://lkml.kernel.org/r/20160927141846.GA6589@kravaSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/build/Makefile

5e50426d - tools build: Use fixdep with OUTPUT path prefix

Thu, 26 Nov 2015 18:50:55 +0000

tools build: Use fixdep with OUTPUT path prefixAdding OUTPUT path prefix for fixdep target so we use it properly in outof tree builds.If the fixdep already existed in the tree, the out of tree build wouldsee it already exist and did not build the out of tree version, asreported by Arnaldo: [acme@zoo linux]$ make O=/tmp/build/perf -C tools/perf make: Entering directory '/home/git/linux/tools/perf' BUILD: Doing 'make -j4' parallel build make[2]: Nothing to be done for 'fixdep'. make: Leaving directory '/home/git/linux/tools/perf'Reported-and-Tested-by: Arnaldo Carvalho de Melo Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra Cc: Wang Nan Link: http://lkml.kernel.org/r/20151126185055.GC19410@krava.brq.redhat.com[ Fixed conflict with 5725dd8fa888 ("tools build: Clean CFLAGS and LDFLAGS for fixdep") ]Signed-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/build/Makefile

9f7ef985 - tools build: Add fixdep dependency helper

Wed, 23 Sep 2015 10:33:58 +0000

tools build: Add fixdep dependency helperFor dependency tracking we currently use targets that fall out of thegcc -MD command. We store this info in the .cmd file and include asmakefile during the build.This format put object as target and all the c and header files asdependencies, like: util/abspath.o: util/abspath.c /usr/include/stdc-predef.h util/cache.h \ /usr/include/bits/wordsize.h /usr/include/gnu/stubs.h \ ...If any of those dependency header files (krava.h below) is removed thebuild fails on: make[1]: *** No rule to make target 'krava.h', needed by 'inc.o'. Stop.This patch adds fixdep helper, that is used by kbuild to alter the shapeof the object dependencies like: source_util/abspath.o := util/abspath.c deps_util/abspath.o := \ /usr/include/stdc-predef.h \ util/cache.h \ ... util/abspath.o: $(deps_util/abspath.o) $(deps_util/abspath.o):With this format the header removal won't make the build fail, becauseit'll be picked up by the last empty target defined for each header.As previously mentioned the fixdep tool is taken from kbuild. It's notcomplete backport, only the part that alters the standard dependencyinfo was taken, the part that adds the CONFIG_* dependency logic will beprobably taken later on.Signed-off-by: Jiri Olsa Cc: David Ahern Cc: Kai Germaschewski Cc: Namhyung Kim Cc: Peter Zijlstra Link: http://lkml.kernel.org/r/1443004442-32660-4-git-send-email-jolsa@kernel.orgSigned-off-by: Arnaldo Carvalho de Melo List of files: /linux-6.15/tools/build/Makefile