diff options
author | Rasmus Villemoes <linux@rasmusvillemoes.dk> | 2021-03-05 13:02:12 +0300 |
---|---|---|
committer | Masahiro Yamada <masahiroy@kernel.org> | 2021-04-24 23:12:32 +0300 |
commit | 0b956e204132ce3fe4221a062638bf83a30e6200 (patch) | |
tree | d9da74a93307567eb8390c1a72a2e040974c7ea3 /scripts/Makefile.build | |
parent | 5cc1247204616528b427e276c97c5bc4c9612347 (diff) | |
download | linux-0b956e204132ce3fe4221a062638bf83a30e6200.tar.xz |
kbuild: apply fixdep logic to link-vmlinux.sh
The patch adding CONFIG_VMLINUX_MAP revealed a small defect in the
build system: link-vmlinux.sh takes decisions based on CONFIG_*
options, but changing one of those does not always lead to vmlinux
being linked again.
For most of the CONFIG_* knobs referenced previously, this has
probably been hidden by those knobs also affecting some object file,
hence indirectly also vmlinux.
But CONFIG_VMLINUX_MAP is only handled inside link-vmlinux.sh, and
changing CONFIG_VMLINUX_MAP=n to CONFIG_VMLINUX_MAP=y does not cause
the build system to re-link (and hence have vmlinux.map
emitted). Since that map file is mostly a debugging aid, this is
merely a nuisance which is easily worked around by just deleting
vmlinux and building again.
But one could imagine other (possibly future) CONFIG options that
actually do affect the vmlinux binary but which are not captured
through some object file dependency.
To fix this, make link-vmlinux.sh emit a .vmlinux.d file in the same
format as the dependency files generated by gcc, and apply the fixdep
logic to that. I've tested that this correctly works with both in-tree
and out-of-tree builds.
Signed-off-by: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Diffstat (limited to 'scripts/Makefile.build')
0 files changed, 0 insertions, 0 deletions