From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-bw0-f227.google.com ([209.85.218.227]:34331 "EHLO mail-bw0-f227.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754059AbZKHVlI (ORCPT ); Sun, 8 Nov 2009 16:41:08 -0500 Message-ID: <4AF7397D.2050202@gmail.com> Date: Sun, 08 Nov 2009 22:34:53 +0100 From: Carmelo Amoroso Reply-To: carmelo73@gmail.com MIME-Version: 1.0 Subject: [PATCH] kbuild: Allow to use depmod from a non default install Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kbuild-owner@vger.kernel.org List-ID: To: Linux Kernel Mailing List Cc: linux-kbuild This patch allow to specify the directory where to find the depmod tool other than being forced to use the module-init-tools installed on the host. The reason for this is explained below. When doing cross-compilation, it not guaranteed that the module-init-tools installed on the host (and used during kernel build) are exactly the same and compatible with those used on the target at runtime. For example, recent changes in how depmod writes modules.dep using root-less path, make older modprobe unusable on the target. User in ths case could install in a different path the module-init-tools compatible with the version used on the target and specify the path on the command line. Signed-off-by: Carmelo Amoroso --- Makefile | 3 ++- 1 files changed, 2 insertions(+), 1 deletions(-) diff --git a/Makefile b/Makefile index b4c04f7..f5286c4 100644 --- a/Makefile +++ b/Makefile @@ -316,7 +316,8 @@ OBJDUMP = $(CROSS_COMPILE)objdump AWK = awk GENKSYMS = scripts/genksyms/genksyms INSTALLKERNEL := installkernel -DEPMOD = /sbin/depmod +DEPMOD_PATH ?= /sbin +DEPMOD = $(DEPMOD_PATH)/depmod KALLSYMS = scripts/kallsyms PERL = perl CHECK = sparse -- 1.6.3.3