diff options
author | Masahiro Yamada <masahiroy@kernel.org> | 2021-03-25 21:54:09 +0300 |
---|---|---|
committer | Masahiro Yamada <masahiroy@kernel.org> | 2021-04-24 23:17:02 +0300 |
commit | 69bc8d386aebbd91a6bb44b6d33f77c8dfa9ed8c (patch) | |
tree | d3f29eb4a12db432954a82a46a1b3b324e82f88b /drivers/mfd/arizona.h | |
parent | 987fdfec24102a151c032c467e51c7f0d6d18af9 (diff) | |
download | linux-69bc8d386aebbd91a6bb44b6d33f77c8dfa9ed8c.tar.xz |
kbuild: generate Module.symvers only when vmlinux exists
The external module build shows the following warning if Module.symvers
is missing in the kernel tree.
WARNING: Symbol version dump "Module.symvers" is missing.
Modules may not have dependencies or modversions.
I think this is an important heads-up because the resulting modules may
not work as expected. This happens when you did not build the entire
kernel tree, for example, you might have prepared the minimal setups
for external modules by 'make defconfig && make modules_preapre'.
A problem is that 'make modules' creates Module.symvers even without
vmlinux. In this case, that warning is suppressed since Module.symvers
already exists in spite of its incomplete content.
The incomplete (i.e. invalid) Module.symvers should not be created.
This commit changes the second pass of modpost to dump symbols into
modules-only.symvers. The final Module.symvers is created by
concatenating vmlinux.symvers and modules-only.symvers if both exist.
Module.symvers is supposed to collect symbols from both vmlinux and
modules. It might be a bit confusing, and I am not quite sure if it
is an official interface, but presumably it is difficult to rename it
because some tools (e.g. kmod) parse it.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Diffstat (limited to 'drivers/mfd/arizona.h')
0 files changed, 0 insertions, 0 deletions