Re: modules.dep and depmod.pl

["Linus Walleij" <linus.ml.walleij@gmail.com>]

2008/6/14 Matthieu castet <castet.matthieu@free.fr>:

> What's wrong with using your host depmod to build it.
> When I build a crosscompilation kernel, and I do make module_install,
> modules.dep are generated.

Well I do believe that works for you because you're lucky to
have a host with a recent kernel and module-init-tools.

However I believe that creates an unsound relation between the
host depmod and any cross compilation.

Currently I try to cross-compile a 2.6.25 kernel on an old good
workhorse with a 2.4.x kernel & likewise antique depmod. It
just won't work.

I tried to cross-compile all module-init-tools with --build=i386,
--host=i386, --target=arm-linux,
but that still fails: it checks what version of the kernel it's working
on, and determines that since that is a 2.4.x version it needs
to execute depmod.old instead :-P (Perhaps this is bug?)

I'd _really_ prefer cross-compilation to use the cross compiler
and in-kernel tools only, and currently I think it is actually
only depmod that deviates from that. (OK some scripts may
need a recent version of perl or so, that was just discussed in
another thread.)

Do you think an attempt to patch busybox:s depmod.pl into
scripts/ for the benefit of cross-compilation would be frowned
upon?

Linus Walleij