[PATCH v5 11/14] module: update timestamp of modules.order after modules are built
Thomas Weißschuh <[email protected]>
| Newsgroups | org.kernel.vger.linux-integrity,org.kernel.vger.bpf,org.kernel.vger.linux-arch,org.kernel.vger.linux-doc,org.kernel.vger.linux-kbuild,org.kernel.vger.linux-kernel,org.kernel.vger.linux-modules,org.kernel.vger.linux-security-module,org.ozlabs.lists.linuxppc-dev |
|---|---|
| Message-ID | <[email protected]> |
Make sure that modules.order is always newer than the module .ko files. Other rules can then use modules.order as a prerequisite and rerun if any module is (re-)built. Signed-off-by: Thomas Weißschuh <[email protected]> --- scripts/Makefile.modfinal | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/scripts/Makefile.modfinal b/scripts/Makefile.modfinal index b09040ccddd2..44a382689a5a 100644 --- a/scripts/Makefile.modfinal +++ b/scripts/Makefile.modfinal @@ -66,6 +66,13 @@ endif targets += $(modules:%.o=%.ko) $(modules:%.o=%.mod.o) .module-common.o +# Update modules.order when a module is (re-)built. +# Allow using it as target dependency. +targets += modules.order +__modfinal: modules.order +modules.order: $(modules:%.o=%.ko) + @touch $@ + # Add FORCE to the prerequisites of a target to force it to be always rebuilt. # --------------------------------------------------------------------------- -- 2.54.0