Sarvesh81

Hi all,

I am trying to buid driver modules against a custom kernel.
Actually with the same source modules are generated for 2.6 kernel source.
But when i do make with PATH set to kernel, make completes but no modules are generated for mu custom kernel.
Any idea on how to trace the issue.

Regards
Sarvesh

Segfault

Did make give you any error messages? If not, where did you look for your freshly built modules?

__________________
How To Ask Questions The Smart Way

Sarvesh81

Hi,
Actually trying to build ath9k modules against 2.4.20 version kernel.
But when make is done against 2.6.30 kernel, it succeds generating modules in
compat-wireless/drivers/wireless/ath9k folder.


Regards
Sarvesh

Sarvesh81

Hi,

Here is the log for make:
**********************************
make KLIB=/home/prasad/project_peacock/new_lsp_blore/linux-2.4.20_mvl31_new KLIB_BUILD=/home/prasad/project_peacock/new_lsp_blore/linux-2.4.20_mvl31_new
make: *** No rule to make target `kernelversion'. Stop.
/bin/sh: line 1: test: -lt: unary operator expected
make: *** No rule to make target `kernelversion'. Stop.
/bin/sh: line 1: test: -eq: unary operator expected
make: *** No rule to make target `kernelversion'. Stop.
/bin/sh: line 1: test: -ge: unary operator expected
make: *** No rule to make target `kernelversion'. Stop.
./scripts/gen-compat-autoconf.sh config.mk > include/linux/compat_autoconf.h
make[1]: *** No rule to make target `kernelversion'. Stop.
./scripts/gen-compat-autoconf.sh: line 182: [: -le: unary operator expected
make: *** No rule to make target `kernelversion'. Stop.


Regards
Sarvesh

waterhead

I doubt that this would ever work. There are too many differences in a 2.4 kernel. You can't even install the compat-wireless drivers on earlier 2.6 kernels, because of kernel changes.

__________________
Paul

Please do not PM me with requests for help. I will not reply.

Segfault

Yep, that would be correct, if I recall correctly 2.4 did not have in-kernel wireless stack.