Seems to be a conflict with vanilla-sources-2.6.19-rc5. re-emerge of fuse failed with errors: [...] CC [M] /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/dev.o CC [M] /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/dir.o CC [M] /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/file.o CC [M] /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/inode.o CC [M] /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/control.o LD [M] /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/fuse.o Building modules, stage 2. MODPOST 1 modules CC /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/fuse.mod.o LD [M] /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/fuse.ko make[1]: quittant le r
Seems to be a conflict with vanilla-sources-2.6.19-rc5. re-emerge of fuse failed with errors: [...] CC [M] /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/dev.o CC [M] /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/dir.o CC [M] /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/file.o CC [M] /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/inode.o CC [M] /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/control.o LD [M] /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/fuse.o Building modules, stage 2. MODPOST 1 modules CC /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/fuse.mod.o LD [M] /var/tmp/portage/sys-fs/fuse-2.6.0/work/fuse-2.6.0/kernel/fuse.ko make[1]: quittant le répertoire « /usr/src/linux-2.6.19-rc5 » >>> Source compiled. --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-sys-fs_-_fuse-2.6.0-5387.log" open_wr: /usr/src/linux-2.6.19-rc5/astest10460.out open_wr: /usr/src/linux-2.6.19-rc5/astest10464.out open_wr: /usr/src/linux-2.6.19-rc5/astest10474.out open_wr: /usr/src/linux-2.6.19-rc5/astest10478.out -------------------------------------------------------------------------------- It does compile the module, but it cannot merge it... I don't know why....
*** This bug has been marked as a duplicate of 149307 ***