On 2/3/06, Σωτήριο Κοντογιάννη <skontog@xxxxxxxxxx> wrote:
no need to use CFLAGS here i guess , simply use gcc=gcc32 and then export the gcc variable.
now recompile.
This will do the trick .
hope it helps.
good luck :-)
Message from Perego Paolo Franco <p.perego@xxxxxxxx>:
> Does the magic string match your running kernel or are you compiling the
> module with a different kernel source ball?
>
Yes you were right!!. I set in my code:
MODULE_INFO(vermagic,VERMAGIC_STRING);
the VERMAGIC_STRING to the output of :
#strings ex0.ko|grep vermagic
and the result was:
insmod: error inserting './ex0.ko': -1 Invalid module format
with a dmesg message:
ex0: version magic '2.6.11 gcc-4.0' should be '2.6.11 gcc-3.3'
I then realised that I compiled my kernel with gcc-3.3 and later on
I installed gcc-4.0. Now the gcc link points at gcc-4.0 . Is there
a flag for the Makefile CFLAGS to tell the compiler to choose the
gcc-3.3 version instead (CC=gcc-3.3)?
no need to use CFLAGS here i guess , simply use gcc=gcc32 and then export the gcc variable.
now recompile.
This will do the trick .
hope it helps.
good luck :-)
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
--
play the game
