Driver porting: compiling external modules
Driver porting: compiling external modules
Posted Feb 13, 2003 0:17 UTC (Thu) by pedretti (guest, #9593)Parent article: Driver porting: compiling external modules
This is probably a dumb question, but what is the module that you insmod? When I compile the hello_world I get a hello_world.o and a hello_world.ko. Both of these can be insmod'ed but the hello_world.o give an error "no version magic, tainting kernel" -- so I assume the hello_world.ko is the one I want to use?
Posted Apr 30, 2003 20:19 UTC (Wed)
by krobidea (guest, #10955)
[Link]
- RedHat 7.3 out of the box (2.4.18-3 w/.config or any .o files). Compilation fails, thinking that module support is not compiled in. - Version 2.4.20 I built and installed. Compilation failed, *** No rule to make target `modules'. This happens when make changed back to my working directory and did a make xxx modules. The kernel source base Makefile appears to be different in the 2.5.x versions. So, will external modules require that the source be present, built and running? I don't believe any RedHat distributions will work. What about the 2.4 or 2.2 target modules issue?
It seems that this 2.5 method of compiling external modules does not work on older kernel versions. I tried the example .c and Makefile, and got the following results:Driver porting: compiling external modules