[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <490A46D5-834E-46A9-9106-A31F94344F99@goldelico.com>
Date: Wed, 22 Aug 2018 20:53:46 +0200
From: "H. Nikolaus Schaller" <hns@...delico.com>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: Lucas De Marchi <lucas.demarchi@...fusion.mobi>,
Lucas De Marchi <lucas.de.marchi@...il.com>,
Michal Marek <michal.lkml@...kovi.net>,
Jessica Yu <jeyu@...nel.org>,
Chih-Wei Huang <cwhuang@...ux.org.tw>,
stable <stable@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Discussions about the Letux Kernel
<letux-kernel@...nphoenux.org>
Subject: please revert commit ce8556cca6 "kbuild: verify that $DEPMOD is installed" introduced in v4.18.4.
This patch requires that /sbin/depmod is installed and installable on
the build host.
But not all build hosts for cross compiling Linux are Linux systems
and are able to provide a working port of depmod, especially at the
file patch /sbin/depmod.
I use, for example, a Darwin system to cross compile Linux and I run
depmod -a on the embedded system once, after installing a new Linux
kernel there.
I have no problem with seeing a warning, but aborting the build process
is IMHO a bad idea since the previous behaviour didn't harm many people
as far as I see. Probably 99% of people compiling Linux kernels do that
on Linux and 99% of those have depmod installed for optimal operation of
their build host. So IMHO printing the warning is good enough.
BR and thanks,
Nikolaus Schaller
Powered by blists - more mailing lists