[PATCH] modules: Allow to use depmod from a non default install

[PATCH] modules: Allow to use depmod from a non default install

[Carmelo Amoroso]

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

Re: [PATCH] modules: Allow to use depmod from a non default install

[Carmelo Amoroso]

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

Re: [PATCH] modules: Allow to use depmod from a non default install

[Américo Wang]

On Sun, Nov 08, 2009 at 10:44:04PM +0100, 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>

Acked-by: WANG Cong <xiyou.wangcong@gmail.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
>--
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at  http://www.tux.org/lkml/

-- 
Live like a child, think like the god.
 

Re: [PATCH] modules: Allow to use depmod from a non default install

[Carmelo Amoroso]

Américo Wang wrote:
> On Sun, Nov 08, 2009 at 10:44:04PM +0100, 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>
> 
> Acked-by: WANG Cong <xiyou.wangcong@gmail.com>
> 
> 

Hi,
any plan to get it included ?

cheers,
carmelo

>> ---
>> 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
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at  http://www.tux.org/lkml/
> 

Re: [PATCH] modules: Allow to use depmod from a non default install

[Américo Wang]

On Sat, Nov 21, 2009 at 04:02:14PM +0100, Carmelo Amoroso wrote:
>Américo Wang wrote:
>> On Sun, Nov 08, 2009 at 10:44:04PM +0100, 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>
>> 
>> Acked-by: WANG Cong <xiyou.wangcong@gmail.com>
>> 
>> 
>
>Hi,
>any plan to get it included ?
>

Hi,

I am not the maintainer, Sam was supposed to take this, but
yesterday, he just gave his position out. So I expect Andrew
or someone can take this.

Thanks.

-- 
Live like a child, think like the god.
 

Re: [PATCH] modules: Allow to use depmod from a non default install

[Carmelo AMOROSO]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/21/2009 4:02 PM, Carmelo Amoroso wrote:
> Américo Wang wrote:
>  > On Sun, Nov 08, 2009 at 10:44:04PM +0100, 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>
>  >
>  > Acked-by: WANG Cong <xiyou.wangcong@gmail.com>
>  >
>  >
> 
> Hi,
> any plan to get it included ?
> 
> cheers,
> carmelo
> 
>  >> ---
>  >> 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
>  >> --
>  >> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>  >> the body of a message to majordomo@vger.kernel.org
>  >> More majordomo info at http://vger.kernel.org/majordomo-info.html
>  >> Please read the FAQ at http://www.tux.org/lkml/
>  >
> 
> 

ping... one year later.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk0UTj8ACgkQoRq/3BrK1s99/wCglIZ37nvDw8g0/nKAt5KRsI6W
M9AAnRVGSbEiod4jFCFhwRRxxofakEQa
=ZSKN
-----END PGP SIGNATURE-----