This bug is common to all the module-assistant built modules.
The problem comes from the fact that the compiler you used to build the fuse-source module differs from that used to build your kernel. Run 'cat /proc/version' to see the GCC version used to build your current kernel. Mine said 3.3.6 - which is gcc-3.3. Install that, then the hacky solution for building fuse is: [EMAIL PROTECTED]:# cd /usr/src/modules/fuse/kernel [EMAIL PROTECTED]:# rm .*.cmd *.o *.ko [EMAIL PROTECTED]:# rm /usr/bin/gcc [EMAIL PROTECTED]:# ln -s /usr/bin/gcc-3.3 /usr/bin/gcc [EMAIL PROTECTED]:# module-assistant build fuse --force [EMAIL PROTECTED]:# module-assistant install fuse --force [EMAIL PROTECTED]:# rm /usr/bin/gcc [EMAIL PROTECTED]:# ln -s /usr/bin/gcc-4.0 /usr/bin/gcc (Not sure if removing the .o files, etc, is necessary. Seemed safest to ensure the module was rebuilt.) On my Sid system /usr/bin/gcc points to gcc-4.0 by default - so don't forget to replace the link when you're done. Hope that helps... I tried using "CC=gcc-3.3 m-a build ..." but that failed, I didn't investigate trying to propogate a particular gcc version to the build system although that would be cleaner than messing with the symlinks. Steve -- # Debian System Administration www.debian-administration.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
