On Sat, 19 Jun 2004, Gaurav Dhiman wrote: > > Thanks for suggestions. > Now, I am able to get the module compiled properly without any error. > > I know there were few problems like i used different return types for write and read file operation functions. I did that as earlier compiler was not even recognizing user defined types like ssize_t and loff_t etc, so i placed so i placed standard type int. > > I think the main problem was that I was not mentioning the Include path option to gcc. I have one question on this, why we need to specify the path of include folder, there must be default with gcc settings. Whats the default include path for gcc compiler, i know it will not be in any case the path to include folder in kernel source, because kernel programming is not what gcc is normally made for. > > Anyway thanks for helping me out. It was my first experinece on this list and definitely a good one. > Standard C header files should (must) not be used for kernel compilations. The include files from the kernel source tree are required. Ian -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
