* Roger Oberholtzer (roger@opq.se) [20100825 17:44]:
Isn't /lib/modules where the compiled things wind up? I did not think it was consulted when a module is being compiled.
A correctly written script as for instance the nvidia one uses that symlink as one of several possible plases to look for the sources. /lib/modules/$(uname -r)/build was introduced to point to the sources from which the modules for the specified kernel were built.
Things in /lib/modules have already completed the compilation step. So I am talking about earlier in the chain of events.
Have you actually looked at the output of ls -ld /lib/modules/$(uname -r)/build ? I guess not as otherwise you wouldn't state the above. When compiling modules for a given kernel, the most interesting things are the path to the sources and the files generated when building the kernel. On an openSUSE system these differ because we want to build drivers for multiple kernel flavours from the same sources. Therefor the autogenerated files and the necessary makefile are stored below /usr/src/linux-obj/<architecture>/<kernel_flavour/ A correctly written script will use the second method described in the README.suse I mentioned to build an external module. Philipp -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org