Thanks for everyone's replies on this. Much appreciated. I've built
the module using gcc-3.4 and it's inserted into the kernel happily
enough. (by changing the gcc symlink)
When building, it offered up a few warnings about casting ints to
different sizes to pointers. Because of this I was expecting it to just
segfault the kernel, but it seems to insert without incident. I'll look
at these errors later, when stuff starts to break :)
I'm now having problems with linking some 32bit apps and I'll post
another mail/thread. But thanks for the help so far.
Cheers,
James
Mike Dobbs wrote:
As far as I know, the kernel and its modules need to be build with the
same version of gcc. If your kernel was build with 3.4 (see
/proc/version), then you need to download gcc-3.4 and compile the
modules with gcc-3.4. You'll need to either chance the symbolic link
of /usr/bin/gcc to gcc-3.4 or change your comile options.
----- Original Message ----- From: "James Hansen" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, October 14, 2005 11:28 AM
Subject: Compiling a kernel module. gcc-3.3 vs. gcc-3.4
I'm having problems building and installing a kernel module for the
amd64 port of debian.
It seems that debian is shipped with gcc-3.3 as it's compiler, but it
looks like the amd64 kernel is built with gcc-3.4
(from a syslog message I'm getting when I modprobe a driver)
Oct 14 16:54:39 localhost kernel: mydriver: version magic
'2.6.8-11-amd64-generic gcc-3.3' should be '2.6.8-11-amd64-generic
gcc-3.4'
Is this actually the case, and if so is this going to continue when
this becomes an official debian distribution?
Oh, and also what can I do about this? Do I have to fetch gcc-3.4 to
build kernel modules? (Or rebuild my kernel with gcc-3.3)
Thanks people.
James
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
