diff options
| author | Masahiro Yamada <[email protected]> | 2022-06-23 19:11:47 +0000 |
|---|---|---|
| committer | Masahiro Yamada <[email protected]> | 2022-06-25 21:15:05 +0000 |
| commit | 53632ba87d9f302a8d97a11ec2f4f4eec7bb75ea (patch) | |
| tree | 0e098890b4adbaf2bf500fe2ad3e723993cfc9d6 /scripts/clang-tools/gen_compile_commands.py | |
| parent | Documentation/llvm: Update Supported Arch table (diff) | |
| download | kernel-53632ba87d9f302a8d97a11ec2f4f4eec7bb75ea.tar.gz kernel-53632ba87d9f302a8d97a11ec2f4f4eec7bb75ea.zip | |
kbuild: link vmlinux only once for CONFIG_TRIM_UNUSED_KSYMS (2nd attempt)
If CONFIG_TRIM_UNUSED_KSYMS is enabled and the kernel is built from
a pristine state, the vmlinux is linked twice.
Commit 3fdc7d3fe4c0 ("kbuild: link vmlinux only once for
CONFIG_TRIM_UNUSED_KSYMS") explains why this happens, but it did not fix
the issue at all.
Now I realized I had applied a wrong patch.
In v1 patch [1], the autoksyms_recursive target correctly recurses to
"$(MAKE) -f $(srctree)/Makefile autoksyms_recursive".
In v2 patch [2], I accidentally dropped the diff line, and it recurses to
"$(MAKE) -f $(srctree)/Makefile vmlinux".
Restore the code I intended in v1.
[1]: https://lore.kernel.org/linux-kbuild/[email protected]/
[2]: https://lore.kernel.org/linux-kbuild/[email protected]/
Fixes: 3fdc7d3fe4c0 ("kbuild: link vmlinux only once for CONFIG_TRIM_UNUSED_KSYMS")
Signed-off-by: Masahiro Yamada <[email protected]>
Tested-by: Sami Tolvanen <[email protected]>
Reviewed-by: Nick Desaulniers <[email protected]>
Diffstat (limited to 'scripts/clang-tools/gen_compile_commands.py')
0 files changed, 0 insertions, 0 deletions