From: Carmelo Amoroso <carmelo73@gmail.com>
To: Carmelo Amoroso <carmelo73@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Carmelo AMOROSO <carmelo.amoroso@st.com>
Subject: Re: [PATCH] modules: Allow to use depmod from a non default install
Date: Sun, 08 Nov 2009 22:56:35 +0100 [thread overview]
Message-ID: <4AF73E93.9020804@gmail.com> (raw)
In-Reply-To: <4AF73BA4.3000501@gmail.com>
Carmelo Amoroso wrote:
> 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 <carmelo.amoroso@st.com>
> ---
> 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
>
Apologies for duplicated emails.
Please discard this last one.
Regards,
Carmelo
next prev parent reply other threads:[~2009-11-08 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 21:44 Carmelo Amoroso
2009-11-08 21:56 ` Carmelo Amoroso [this message]
2009-11-09 3:06 ` Américo Wang
2009-11-21 15:02 ` Carmelo Amoroso
2009-11-21 17:08 ` Américo Wang
2010-12-24 7:39 ` Carmelo AMOROSO
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=4AF73E93.9020804@gmail.com \
--to=carmelo73@gmail.com \
--cc=carmelo.amoroso@st.com \
--cc=linux-kernel@vger.kernel.org \
/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
Powered by JetHome