[Buildroot] [PATCH] linux: run depmod only if modules directory exists

Peter Korsgaard peter at korsgaard.com
Sat Aug 29 17:43:47 UTC 2020


>>>>> "Yann" == Yann E MORIN <yann.morin.1998 at free.fr> writes:

 > Paul, All,
 > On 2020-06-23 13:38 +0200, Paul Cercueil spake thusly:
 >> If the modules directory that corresponds to the version of the kernel
 >> being built has been deleted, don't try to run depmod, which will
 >> obviously fail.
 >> 
 >> This can happen for instance when the modules are stripped from the main
 >> root filesystem, and placed into a separate filesystem image, so that
 >> the root filesystem and the kernel can be updated separately.
 >> 
 >> Signed-off-by: Paul Cercueil <paul at crapouillou.net>
 >> ---
 >> linux/linux.mk | 3 ++-
 >> 1 file changed, 2 insertions(+), 1 deletion(-)
 >> 
 >> diff --git a/linux/linux.mk b/linux/linux.mk
 >> index b90b032bb9..d31933fea1 100644
 >> --- a/linux/linux.mk
 >> +++ b/linux/linux.mk
 >> @@ -490,7 +490,8 @@ endef
 >> # Run depmod in a target-finalize hook, to encompass modules installed by
 >> # packages.
 >> define LINUX_RUN_DEPMOD
 >> -	if grep -q "CONFIG_MODULES=y" $(LINUX_DIR)/.config; then \
 >> +	if test -d $(TARGET_DIR)/lib/modules/$(LINUX_VERSION_PROBED) \

 > Removing stuff from target and then expecting everything continues to
 > work as expected is a bit hackish, I believe. But another maintainer
 > was OK with that patch, so applied to master now, thanks.

Committed to 2020.02.x and 2020.05.x, thanks.

-- 
Bye, Peter Korsgaard



More information about the buildroot mailing list