brew doctor and libmacfuse/libosxfuse

gistfile1.txt

If you see...

Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected dylibs:
    /usr/local/lib/libmacfuse_i32.2.dylib    /usr/local/lib/libmacfuse_i64.2.dylib    /usr/local/lib/libosxfuse_i32.2.dylib    /usr/local/lib/libosxfuse_i64.2.dylib
Warning: Unbrewed .la files were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .la files:
    /usr/local/lib/libosxfuse_i32.la    /usr/local/lib/libosxfuse_i64.la
Warning: Unbrewed .pc files were found in /usr/local/lib/pkgconfig.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .pc files:
    /usr/local/lib/pkgconfig/osxfuse.pc

The fix is:

cd /usr/local
tar -cvzf macfuse-backup.tar.gz \
    lib/libmacfuse_i32.2.dylib \
    lib/libmacfuse_i64.2.dylib \
    lib/libosxfuse_i32.2.dylib \
    lib/libosxfuse_i64.2.dylib \
    lib/libosxfuse_i32.la \
    lib/libosxfuse_i64.la \
    lib/pkgconfig/osxfuse.pc \

rm -f lib/libmacfuse_i32.2.dylib \
    lib/libmacfuse_i64.2.dylib \
    lib/libosxfuse_i32.2.dylib \
    lib/libosxfuse_i64.2.dylib \
    lib/libosxfuse_i32.la \
    lib/libosxfuse_i64.la \
    lib/pkgconfig/osxfuse.pc

brew prune

brew install fuse4x

Does ist make much sense, to remove the backup you created the step before?

I would rather consider

rm -f lib/libmacfuse_i32.2.dylib
lib/libmacfuse_i64.2.dylib
lib/libosxfuse_i32.2.dylib
lib/libosxfuse_i64.2.dylib
lib/libosxfuse_i32.la
lib/libosxfuse_i64.la
lib/pkgconfig/osxfuse.pc

Watch out for not to crash TrueCrypt by removing these libs.
Rest works fine.

You're right. I updated the gist. Thanks!

That's wrong. fuse4x is obsolete and should not be used.

Any suggestions on what should be used instead of fuse4x? A comment like that could be more helpful if it explained an alternative or why it's now considered obsolete ...

Ya, to echo @yumitsu + @snnd, this strategy will completely hose TrueCrypt. It's been a reported issue since February of 2012: #10183 #14430 #15399, but I think no one's sure how to fix it downstream from TrueCrypt (who doesn't seem to care).

Thanks @jm3. I didn't realize that @yumitsu and @snnd where ultimately referencing the same problem(s). From my reading of the comments before, @yumitsu's suggestion doesn't eliminate fuse4x and still causes problems with TrueCrypt. Forgive my lack of understanding here, this is all new to me. I guess my ultimate question is really is there a newer or more appropriate thing to use in fuse4x's place if it's considered obsolete?

This script fixed the brew doctor warnings for me, and Truecrypt still seems to work.

Trinitronx script worked for me too. No more warnings from Brew Doctor and Truecrypt continues to work.

@trinitronx worked great for me!

@trinitronx worked properly in my case, too. Thanks!

It works for me too! Thanks!

Thx! work solution

I have the same problem with Bitcasa I guess they use the same fuse as TrueCrypt

What is the actually problem here? Why does the solution work?

Here is a solution I created from a bash script made to solve the same issue: https://gist.github.com/SteveBenner/10938596.

It uses Ruby module FileUtils, but falls back to shell commands if you can't include the module for some reason. It also prevents you from running the script if you don't need to. Works like a charm for me.

thanks a lot stevebenner that solved it really easily for me.

This little snippet demonstrates nicely the idea, but it lacks important verifications, symlinks aren't copied over and the pkgconfig files aren't moved to the right subdir.
Fixed, tested on Yosemite the gist is here.
Thanx to Aaron, James and Yiufung . enjoy...