Re: unresolved kernel symbols

[Tong <mlist4suntong@yahoo.com>]

Thanks Kevin for the reply.

On Wed, 11 Aug 2004 09:13:23 -0400, Kevin B. McCarty wrote:

>> I am experiencing unresolved kernel symbol problem
>> when compiling my pctel modem driver. 
>> 
>> The compilation and installation was ok. When trying
>> to load the module, I get:
>> 
>> % insmod -f pctel
>> Using /lib/modules/2.4.25-1-386/misc/pctel.o Warning:
>> The module you are
>> trying to load
>> (/lib/modules/2.4.25-1-386/misc/pctel.o) is compiled
>> with a
>> gcc version 2 compiler, while the kernel you are
>> running is compiled with
>> a gcc version 3 compiler. This is known to not work.
> 
> Is the claim of the error message true -- that you compiled the module
> with gcc-2.95?  This may have happened unintentionally if, for instance,
> /usr/bin/cc or /usr/bin/gcc was a symlink to gcc-2.95 on your system.
> If so, then the obvious fix is to make cc and gcc be symlinks to gcc-3.3
> (this should be the case by default in sarge and sid) and recompile.

Oh, I always get that compiler version warning for gcc3. 

I've double checked, seems that I only have gcc3 installed:

$ dpkg -l | grep gcc
ii  gcc            3.3.4-2        The GNU C compiler
ii  gcc-3.3        3.3.4-3        The GNU C compiler
ii  gcc-3.3-base   3.3.4-3        The GNU Compiler Collection (base package)
ii  libgcc1        3.3.4-3        GCC support library

$ cc --version
cc (GCC) 3.3.4 (Debian 1:3.3.4-3)

~$ gcc --version
gcc (GCC) 3.3.4 (Debian 1:3.3.4-3)

When I get those "unresolved kernel symbols" in RH, I need to "prepare
the kernel source" -- those "make xconfig" stuffs. Do I have to do the
same in Debian?