[root@localhost]~/kernel-stu/hello-1# make
make -C /lib/modules/2.6.23.1-42.fc8/build M=/root/kernel-stu/hello-1 modules
make[1]: Entering directory `/usr/src/kernels/2.6.23.1-42.fc8-i686'
Building modules, stage 2.
MODPOST 0 modules
make[1]: Leaving directory `/usr/src/kernels/2.6.23.1-42.fc8-i686'
Solution: review the Makefile of the source code, any of the following can get this error:
First:
[root@localhost]~/kernel-stu/hello-1# cat Makefile
bj-m += hello-1.o
all:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean
Second:
[root@localhost]~/kernel-stu/hello-1# cat Makefile
obj-m += hello-1.c
all:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean
The right content of Makefile is:
[root@localhost]~/kernel-stu/hello-1# cat Makefile
obj-m += hello-1.o
all:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) modules
clean:
make -C /lib/modules/$(shell uname -r)/build M=$(PWD) clean
The content of hello-1.c:
[root@localhost]~/kernel-stu/hello-1# cat hello-1.c
#include <linux/init.h>
#include <linux/module.h>
MODULE_LICENSE("Dual BSD/GPL");
static int hello_init(void){
printk(KERN_ALERT "hello,world\n");
return 0;
}
static void hello_exit(void){
printk(KERN_ALERT "goodbye,cruel world\n");
return 0;
}
module_init(hello_init);
module_exit(hello_exit);
Make:
[root@localhost]~/kernel-stu/hello-1# make
make -C /lib/modules/2.6.23.1-42.fc8/build M=/root/kernel-stu/hello-1 modules
make[1]: Entering directory `/usr/src/kernels/2.6.23.1-42.fc8-i686'
CC [M] /root/kernel-stu/hello-1/hello-1.o
/root/kernel-stu/hello-1/hello-1.c: In function ‘hello_exit’:
/root/kernel-stu/hello-1/hello-1.c:13: warning: ‘return’ with a value, in function returning void
Building modules, stage 2.
MODPOST 1 modules
CC /root/kernel-stu/hello-1/hello-1.mod.o
LD [M] /root/kernel-stu/hello-1/hello-1.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.23.1-42.fc8-i686'
-------------------------------------------------------------
the kernel build system (kbuild) allows to compile modules whose sources
live outside the kernel source tree by setting SUBDIRS as follows (from
the module sources's directory):
$ make -C /lib/modules/$(uname -r)/build modules SUBDIRS=$(pwd)
people use this mechanism to compile kernel modules that are missing in
their kernel sources, or have been updated/fixed in the meantime.
Currently there are a number of deficiencies for building such modules:
(1) symbol versioning (MODVERSIONS) is not properly supported, and
(2) only the `modules' make target is supported.
Problem (1) did not exist in the 2.4 kernel series. The current
situation has lead authors of several external modules to implement some
of the kbuild functionality in their own makefiles, which can only lead
to problems later on.
During the kernel compile, a list of all files that export symbols is
created in .tmp_versions/ of the kernel source tree. After everything is
compiled, the module versions of all these object files are resolved
with modpost. When an external module is compiled, it ends up being the
only file in .tmp_versions/, and so symbols in other modules would not
be found.
An additional problem is that resolving symbol versions requires all
module files plus vmlinux to be in the kernel source tree, so modules
cannot be build against a clean kernel source tree.
Reference :
lwn.net/Articles/69148/
ubuntu下hello world kernel Module:MODPOST 0 modules
最新推荐文章于 2023-03-14 13:47:46 发布