Messages in this thread Patch in this message | | | Date | Thu, 12 Dec 2002 01:21:01 -0600 | From | Matt Reppert <> | Subject | Re: 2.5.50 Up and running but |
| |
On Wed, 11 Dec 2002 22:59:10 -0800 Matt Young <wz6b@arrl.net> wrote:
> Boot couldn't find the module dependency file, even though I did make modules > and make modules_install
Yeah, the make rule for depmod got removed in one of the module merges. This will put it back. (Untested, my init scripts run depmod so it's not a big deal for me.) Rusty, am I being stupid or is this okay now that depmod works?
--- a/Makefile Sun Nov 10 19:05:55 2002 +++ b/Makefile Fri Nov 8 20:08:32 2002 @@ -157,7 +157,6 @@ OBJDUMP = $(CROSS_COMPILE)objdump AWK = awk GENKSYMS = /sbin/genksyms +DEPMOD = /sbin/depmod KALLSYMS = /sbin/kallsyms PERL = perl MODFLAGS = -DMODULE @@ -516,7 +515,7 @@ # Install modules .PHONY: modules_install -modules_install: _modinst_ $(patsubst %, _modinst_%, $(SUBDIRS)) +modules_install: _modinst_ $(patsubst %, _modinst_%, $(SUBDIRS)) _modinst_post .PHONY: _modinst_ _modinst_: @@ -524,20 +523,6 @@ @rm -f $(MODLIB)/build @mkdir -p $(MODLIB)/kernel @ln -s $(TOPDIR) $(MODLIB)/build + +# If System.map exists, run depmod. This deliberately does not have a +# dependency on System.map since that would run the dependency tree on +# vmlinux. This depmod is only for convenience to give the initial +# boot a modules.dep even before / is mounted read-write. However the +# boot script depmod is the master version. +ifeq "$(strip $(INSTALL_MOD_PATH))" "" +depmod_opts := +else +depmod_opts := -b $(INSTALL_MOD_PATH) -r +endif +.PHONY: _modinst_post +_modinst_post: + if [ -r System.map ]; then $(DEPMOD) -ae -F System.map $(depmod_opts) $(KERNELRELEASE); fi .PHONY: $(patsubst %, _modinst_%, $(SUBDIRS)) $(patsubst %, _modinst_%, $(SUBDIRS)) : . > Also the make config did not select the right Intel processor
???
> nor is there a mouse driver
What kind of mouse? What config option?
Matt - 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/
| |