Problem while including a module to kernel

Problem while including a module to kernel

[BalaKrishna Mallipeddi]

Hi,
   I am in deep trouble to include a module to kernel.

I am getting the following warnings, errors and hints
while compiling(via makefile) and including the
module(via insmod) to kernel. I am including the log
below for easy reference. Please help me. 
log:
root@(none):/home/chois/rfs_modules/fdisk# make
gcc -Wall -DMODULE -D__KERNEL__ -DLINUX -c
rfs_fdisk_module.c
rfs_fdisk_module.c: In function `rfs_fdisk_module':
rfs_fdisk_module.c:374: warning: implicit declaration
of function `ioctl'
rfs_fdisk_module.c:403: warning: implicit declaration
of function
`reboot'root@(none):/home/chois/rfs_modules/fdisk#
sync
root@(none):/home/chois/rfs_modules/fdisk# insmod
rfs_fdisk_module.o
rfs_fdisk_module.o: unresolved symbol read
rfs_fdisk_module.o: unresolved symbol reboot
rfs_fdisk_module.o: unresolved symbol lseek
rfs_fdisk_module.o: unresolved symbol _exit
rfs_fdisk_module.o: unresolved symbol write
rfs_fdisk_module.o: unresolved symbol ioctl
rfs_fdisk_module.o:
Hint: You are trying to load a module without a GPL
compatible license
      and it has unresolved symbols.  Contact the
module supplier for
      assistance, only they can help you.


I had gone through many questions related to this
"Hint". But i couldn't get any generalized answer. All
are related to a particular context.

Thanks & Regards

=====
BalaKrishna Mallipeddi
Member Technical Staff Software
Innomedia Technologies Pvt. Ltd.,
#3278, 12th Main, HAL 2nd stage,
Bangalore-560008,
INDIA
Phone : 5278389 + 123

__________________________________
Do you Yahoo!?
Yahoo! Calendar - Free online calendar with sync to Outlook(TM).
http://calendar.yahoo.com

Re: Problem while including a module to kernel

[Richard B. Johnson]

On Tue, 10 Jun 2003, BalaKrishna Mallipeddi wrote:

> Hi,
>    I am in deep trouble to include a module to kernel.
>
> I am getting the following warnings, errors and hints
> while compiling(via makefile) and including the
> module(via insmod) to kernel. I am including the log
> below for easy reference. Please help me.
> log:
> root@(none):/home/chois/rfs_modules/fdisk# make
> gcc -Wall -DMODULE -D__KERNEL__ -DLINUX -c
> rfs_fdisk_module.c
> rfs_fdisk_module.c: In function `rfs_fdisk_module':
> rfs_fdisk_module.c:374: warning: implicit declaration
> of function `ioctl'
> rfs_fdisk_module.c:403: warning: implicit declaration
> of function
> `reboot'root@(none):/home/chois/rfs_modules/fdisk#
> sync
> root@(none):/home/chois/rfs_modules/fdisk# insmod
> rfs_fdisk_module.o
> rfs_fdisk_module.o: unresolved symbol read
> rfs_fdisk_module.o: unresolved symbol reboot
> rfs_fdisk_module.o: unresolved symbol lseek
> rfs_fdisk_module.o: unresolved symbol _exit
> rfs_fdisk_module.o: unresolved symbol write
> rfs_fdisk_module.o: unresolved symbol ioctl
> rfs_fdisk_module.o:
> Hint: You are trying to load a module without a GPL
> compatible license
>       and it has unresolved symbols.  Contact the
> module supplier for
>       assistance, only they can help you.
>
>

No! The problem is that what he is trying to load is __not__
a module!

The "hint" is

> rfs_fdisk_module.c:374: warning: implicit declaration
> of function `ioctl'

This is, therefore, not a function within the module, but
something called, perhaps from a runtime library.

It is likely that all the other symbols like read, write, lseek,
etc., are also expected to be resolved by the 'C' runtime library
rather than being internal to the module.


Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.