22 Feb, 2013

1 commit

  • On architectures which have symbol prefixes, depmod emits lots of
    warnings like this:

    WARNING: $module.ko needs unknown symbol $symbol

    This is because depmod isn't being passed the -P
    arguments to specify the symbol prefix to ignore. This option is
    included since the 3.13 release of module-init-tools.

    Update scripts/depmod.sh to take extra arguments for the symbol prefix
    (required but may be empty), and update the main Makefile to always pass
    "$(CONFIG_SYMBOL_PREFIX)" to scripts/depmod.sh.

    If the provided symbol prefix is non-empty, scripts/depmod.sh checks if
    depmod --version reports module-init-tools with a version number < 3.13
    otherwise it appends -P $SYMBOL_PREFIX to the depmod command line.

    Signed-off-by: James Hogan
    Cc: Michal Marek
    Cc: linux-kbuild@vger.kernel.org
    Cc: Mike Frysinger
    Cc: Yoshinori Sato
    Cc: uclinux-dist-devel@blackfin.uclinux.org
    Signed-off-by: Michal Marek

    James Hogan
     

23 Jan, 2012

1 commit

  • scripts/depmod.sh checks for the output of '-V' expecting that it has
    module-init-tools in it. It's a hack to prevent users from using
    modutils instead of module-init-tools, that only works with 2.4.x
    kernels. This however prints an annoying warning for kmod tool, that is
    currently replacing module-init-tools.

    Rather than putting another check for kmod's version, just remove it
    since users of 2.4.x kernel are unlikely to upgrade to 3.x, and if they
    do, let depmod fail in that case because they should know what they are
    doing.

    Signed-off-by: Lucas De Marchi
    Acked-by: WANG Cong
    Acked-By: Kay Sievers
    Signed-off-by: Michal Marek

    Lucas De Marchi
     

12 Jul, 2011

1 commit


10 Jun, 2011

2 commits