The kernel would not report a link error if the problem were a missing architecture in the kext. More likely is that it depends on symbols that are no longer present.
FUSE="/Library/Filesystems/fusefs.fs/Support/fusefs.kext", then please edit your question to include:
- the relevant bits from your kernel log and/or the output from
sudo kextutil -t -v 2 "$FUSE" and
sudo kextutil -t -v 4 "$FUSE"
- the output from
kextlibs -c -all-symbols "$FUSE"
OSBundleLibraries and any
OSBundleLibraries_x86_64 elements of
You should also contact the MacFuse developers, since a link error generally indicates a bug on their end.
ETA: The logs indicate that MacFuse linking falters on the functions
OSRuntimeInitializeCPP. From the
kextlibs output, it looks like these symbols are published in the i368 and ppc kext libraries. It looks like MacFuse relies on some private kernel functions outside of established kernel programming interfaces. Lion (that's what the Darwin 10.7.1 kernel corresponds to, yes? I'm running Mac OS X 10.6.6, and it reports kernel 10.6.0) has apparently changed some things in the kernel, and this has broken MacFuse.
I am glad to hear that SL-NTFS seems to be working well for you.