[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180822191048.GA6916@kroah.com>
Date: Wed, 22 Aug 2018 21:10:48 +0200
From: Greg KH <greg@...ah.com>
To: "H. Nikolaus Schaller" <hns@...delico.com>
Cc: Randy Dunlap <rdunlap@...radead.org>,
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: Re: please revert commit ce8556cca6 "kbuild: verify that $DEPMOD is
installed" introduced in v4.18.4.
On Wed, Aug 22, 2018 at 08:53:46PM +0200, H. Nikolaus Schaller wrote:
> 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.
It needs to be reverted in Linus's tree first before I can revert it in
the stable tree(s).
thanks,
greg k-h
Powered by blists - more mailing lists