Re: 2.5.52 and modules (lots of unresolved symbols)?

Alex Goddard (agoddard@purdue.edu)
Mon, 16 Dec 2002 13:54:21 +0000 (UTC)


On Mon, 16 Dec 2002, Melchior FRANZ wrote:

> * Alex Goddard -- Monday 16 December 2002 19:32:
> > Huh. Like I said, reinstalling the mod tools and doing a rebuild after a
> > make clean cleared it up for me.
> >
> > Weird.
>
> Not really. The problem is, that the kernel Makefile contains
> an absolute path for depmod (/sbin/depmod) which doesn't seem
> like a good idea. I you are installing the module-init-tools
> to /usr/local/sbin, they don't take precedence over the old
> depmod et al.
>
> Why doesn't the Makefile simply define "DEPMOD = depmod"
> instead of "DEPMOD = /sbin/depmod" (and likewise for
> genksyms)?

Ah. That makes sense. Your question is the same as mine, then. Why
define an absolute path for depmod?

One suggestion for the person who started this thread, then, is to make
sure that /sbin/depmod is, or is pointing to, a version of depmod that
won't freak out over the modules.

-- 
Alex Goddard
agoddard@purdue.edu
-
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/