I know the subject sounds like i'm really messing things up but i'm
kind of clue less and any suggestion is appreciated...
The FUSE module was working fine and _suddenly_ it started to
complain, when I try a new install i get the same result so the
problem must be somewhere else
# modprobe fuse
/lib/modules/2.4.21-27.0.2.EL/kernel/fs/fuse/fuse.o: couldn't find the
kernel version the module was compiled for
/lib/modules/2.4.21-27.0.2.EL/kernel/fs/fuse/fuse.o: insmod fuse failed
# modinfo kernel/fuse.o
description: "Filesystem in Userspace"
author: "Miklos Szeredi <miklos@...>"
$ cat /proc/version
Linux version 2.4.21-27.0.2.EL (root@...) (gcc version
3.2.3 20030502 (Red Hat Linux 3.2.3-42)) #1 Tue Jan 18 19:45:27 CST
$ gcc -v
Reading specs from /usr/local/lib/gcc/i686-pc-linux-gnu/3.4.3/specs
Configured with: ./configure --enable-long-long
Thread model: posix
gcc version 3.4.3
mmmm.... the actual gcc and the kernel version are diferent... could
it be the problem ? (mmmm.... but i changed gcc before compiling the
last version of fuse and after that it was ok... )
Thanks for the help,
yeap... it was that.
pd: after that i saw that the Makefile in the fuse/kernel directory
has something like CC =3D gcc which overrides a different gcc if passed
as a variable.... nothing big, but can be tricky to find.
On 8/8/05, jens m. noedler <noedler@...> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Leandro Franco wrote at 08/08/2005 11:10 AM:
> > mmmm.... the actual gcc and the kernel version are diferent... could
> > it be the problem ? (mmmm.... but i changed gcc before compiling
> > the last version of fuse and after that it was ok... )
> Recompile kernel and fuse with the same gcc version.
> I had also strange problemes with different gcc versions:
> Greetings, Jens
> - --
> jens m. noedler
> pgp: 0x9f0920bb
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> -----END PGP SIGNATURE-----
> pd: after that i saw that the Makefile in the fuse/kernel directory
> has something like CC = gcc which overrides a different gcc if passed
> as a variable.... nothing big, but can be tricky to find.
Yes, that's rather stupid. I'll try to make it behave more