Your message dated Mon, 04 Feb 2008 14:01:36 +0100
with message-id <[EMAIL PROTECTED]>
and subject line #454188: fuse-source: module-assistant complains gcc-4.0 can't 
be found for fuser-module
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: fuse-source
Version: 2.7.1-2
Severity: normal


Building the fuse kernel module with

> module-assistant auto-install fuse

will fail with a complaint that gcc-4.0 is missing though my aptitude only
offers me gcc-4.1 and gcc-4.2 with the 4.-series.

As described in the error message

> export RELAX_CC_CHECK=1

temporarily fixes the problem.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.16 (PREEMPT)
Locale: [EMAIL PROTECTED], LC_CTYPE=zh_CN.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages fuse-source depends on:
ii  bzip2                         1.0.3-7    high-quality block-sorting file co
ii  debhelper                     5.0.61     helper programs for debian/rules
ii  make                          3.81-3     The GNU version of the "make" util
ii  module-assistant              0.10.11    tool to make module package creati

fuse-source recommends no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Hello,

The problem is that you're running and old (and now unsupported) kernel that has been built with gcc-4.0. However gcc-4.0 is not in the debin archive anymore so module-assistant complains it can find the same compiler as the one used by the kernel.

The right fix is to update your kernel to the one currently in debian testing/unstable or continue to use this workaround. Another fix: find somewhere debian packages of gcc-4.0 (ie: debian stable or snapshot.debian.net).

Best regards, Adam.


--- End Message ---

Reply via email to