From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] linux: do not run depmod during the installation
Date: Sun, 22 Mar 2020 08:19:38 +0100 [thread overview]
Message-ID: <20200322071938.GP4290@scaer> (raw)
In-Reply-To: <20200321235703.10622-1-unixmania@gmail.com>
Carlos, All,
On 2020-03-21 20:57 -0300, unixmania at gmail.com spake thusly:
> From: Carlos Santos <unixmania@gmail.com>
>
> The kernel "install" target runs depmod by means of a wrapper script
> (scripts/depmod.sh), so passing a dummy depmod (e.g. /dev/null) would
> cause warning messages like this:
>
> DEPMOD 5.4.27
> ./scripts/depmod.sh: 46: /dev/null: Permission denied
> make[2]: *** [Makefile:1326: _modinst_post] Error 126
>
> We can avoid running the script by overriding the cmd_depmod variable,
> which contains the command line to run depmod.
>
> As a safety measure, setting DEPMOD to /bin/false makes the installation
> fail if overriding cmd_depmod does not work in a future kernel version.
Really, what's the problem with running this demod here?
The default AArch64 kernel defconfig takes almost 12 minutes to build on
my machine, and the install, including running depmod, takes just under
14 seconds (including parsing all Buildroot Makefiles!).
So running depmod is hardly a time hog...
>
> Signed-off-by: Carlos Santos <unixmania@gmail.com>
> ---
> CC: Yann E. MORIN <yann.morin.1998@free.fr>
> ---
> linux/linux.mk | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/linux/linux.mk b/linux/linux.mk
> index 2e3ea52053..383d1908d6 100644
> --- a/linux/linux.mk
> +++ b/linux/linux.mk
> @@ -134,7 +134,8 @@ LINUX_MAKE_FLAGS = \
> ARCH=$(KERNEL_ARCH) \
> INSTALL_MOD_PATH=$(TARGET_DIR) \
> CROSS_COMPILE="$(TARGET_CROSS)" \
> - DEPMOD=$(HOST_DIR)/sbin/depmod
> + DEPMOD=/bin/false \
> + cmd_depmod=":"
This is touching the internals of the kernel, so no.
Regards,
Yann E. MORIN.
> ifeq ($(BR2_REPRODUCIBLE),y)
> LINUX_MAKE_ENV += \
> --
> 2.18.2
>
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2020-03-22 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 23:57 [Buildroot] [PATCH] linux: do not run depmod during the installation unixmania at gmail.com
2020-03-22 7:19 ` Yann E. MORIN [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200322071938.GP4290@scaer \
--to=yann.morin.1998@free.fr \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox