I see the following when I run brew doctor:
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/libMonoPosixHelper.dylib
/usr/local/lib/libSFFileMonitor.32.dylib
/usr/local/lib/libSFIPC.32.dylib
/usr/local/lib/libSFIPC.I.dylib
/usr/local/lib/libSFsqlite3.7.4.dylib
/usr/local/lib/libSFSyncEngine.I.dylib
Does anyone have any suggestions on how to approach this warning and potentially fix the problem?
This particular set of files appears to be from Citrix Receiver; I received the exact same message after installing brew, and a bit of googling turned up http://arstechnica.com/civis/viewtopic.php?f=19&t=1188699
I'd recommend leaving them in place unless you no longer need Citrix.
Related
When I run brew doctor command I found the following error. How can I solve this issue?
Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.
Unexpected header files:
/usr/local/include/fakepq.h
/usr/local/include/fakesql.h
/usr/local/include/itcl.h
/usr/local/include/itcl2TclOO.h
/usr/local/include/itclDecls.h
/usr/local/include/itclInt.h
/usr/local/include/itclIntDecls.h
/usr/local/include/itclMigrate2TclCore.h
/usr/local/include/itclTclIntStubsFcn.h
/usr/local/include/mysqlStubs.h
/usr/local/include/odbcStubs.h
/usr/local/include/pqStubs.h
/usr/local/include/tcl.h
/usr/local/include/tclDecls.h
/usr/local/include/tclOO.h
/usr/local/include/tclOODecls.h
/usr/local/include/tclPlatDecls.h
/usr/local/include/tclThread.h
/usr/local/include/tclTomMath.h
/usr/local/include/tclTomMathDecls.h
/usr/local/include/tdbc.h
/usr/local/include/tdbcDecls.h
/usr/local/include/tdbcInt.h
/usr/local/include/tk.h
/usr/local/include/tkDecls.h
/usr/local/include/tkPlatDecls.h
Are those files causing any issues? From brew doctor:
Please note that these warnings are just used to help the Homebrew
maintainers with debugging if you file an issue. If everything you use
Homebrew for is working fine: please don't worry or file an issue;
just ignore this. Thanks!
I have Anaconda and Homebrew installed in OSX. Homebrew provides the following diagnostics.
What is the best way to resolve the potential conflicts between Anaconda and Homebrew? How should they be managed not to cause problems to each other?
$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!
Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.
Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following "config" scripts:
/Users/hhh/anaconda3/bin/curl-config
/Users/hhh/anaconda3/bin/freetype-config
/Users/hhh/anaconda3/bin/gsl-config
/Users/hhh/anaconda3/bin/icu-config
/Users/hhh/anaconda3/bin/krb5-config
/Users/hhh/anaconda3/bin/libpng-config
/Users/hhh/anaconda3/bin/libpng16-config
/Users/hhh/anaconda3/bin/llvm-config
/Users/hhh/anaconda3/bin/ncursesw6-config
/Users/hhh/anaconda3/bin/pcre-config
/Users/hhh/anaconda3/bin/python3-config
/Users/hhh/anaconda3/bin/python3.6-config
/Users/hhh/anaconda3/bin/python3.6m-config
/Users/hhh/anaconda3/bin/xml2-config
/Users/hhh/anaconda3/bin/xslt-config
Warning: Putting non-prefixed findutils in your path can cause python builds to fail.
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/libgcc_ext.10.4.dylib
/usr/local/lib/libgcc_ext.10.5.dylib
/usr/local/lib/libgcc_s_x86_64.1.dylib
/usr/local/lib/libgfortran.3.dylib
/usr/local/lib/libgomp.1.dylib
/usr/local/lib/libnnz11.dylib
/usr/local/lib/libociei.dylib
/usr/local/lib/libocijdbc11.dylib
/usr/local/lib/libquadmath.0.dylib
/usr/local/lib/libwkhtmltox.0.12.4.dylib
Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.
Unexpected header files:
/usr/local/include/wkhtmltox/image.h
/usr/local/include/wkhtmltox/pdf.h
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/libgfortran.la
/usr/local/lib/libgomp.la
/usr/local/lib/libintl.la
/usr/local/lib/libquadmath.la
/usr/local/lib/psqlodbcw.la
Warning: Unbrewed static libraries 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 static libraries:
/usr/local/lib/libgfortran.a
/usr/local/lib/libgomp.a
/usr/local/lib/libquadmath.a
I'm sort of new to programming and in the path of setting the environment ready under Mac OS X Yosemite I ran into some issues under the brew doctor command.
It says
Please note that these warnings are just used to help the Homebrew
maintainers with debugging if you file an issue. If everything you use
Homebrew for is working fine: please don't worry and just ignore them.
Thanks!
but I don't really know what to expect and to avoid future issues I'd like to see the output "Your system is ready to brew"
First I ran the brew purge command with the following output
horus:~ rsmendes$ brew prune
Pruned 0 dead formulae Pruned 136
symbolic links and 4 directories from /usr/local
Now I'm getting dylibs warning. I've read that this is solved by removing this files, but also read that it is possible to break something, and I'm uncertain of how to proceed.
I'm also getting header, unbrewed .la, unbrewed .pc and unbrewed static libraries that all seem to be related to the dylibs mentioned.
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/libfuse4x.2.dylib
/usr/local/lib/libntfs-3g.80.dylib
/usr/local/lib/libntfs.9.0.0.dylib
/usr/local/lib/libublio.1.dylib
When I run brew doctor on my Mac, I get the following warnings:
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/libntfs-3g.80.dylib
/usr/local/lib/libntfs.9.0.0.dylib
/usr/local/lib/libublio.1.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/libntfs-3g.la
/usr/local/lib/libntfs.la
/usr/local/lib/libublio.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/fuse.pc
/usr/local/lib/pkgconfig/libntfs-3g.pc
/usr/local/lib/pkgconfig/libublio.pc
Warning: Unbrewed static libraries 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 static libraries:
/usr/local/lib/libntfs-3g.a
/usr/local/lib/libntfs.a
/usr/local/lib/libublio.a
Warning: You have uncommitted modifications to Homebrew
If this a surprise to you, then you should stash these modifications.
Stashing returns Homebrew to a pristine state but can be undone
should you later need to do so for some reason.
cd /usr/local/Library && git stash && git clean -d -f
I can make out from the above 3 warnings that some of them are related to NTFS-3g and libfuse that I installed without using Homebrew, but other than that I don't know how to fix them.
Should I be worried about these warnings? Also, the last warning about changes made to Homebrew installation also worries me, because I haven't made any changes.
How should I fix these warnings?
First of all, these are warnings only, so if nothing is broken it might be prudent to do nothing.
If you don't need ntfs-3g and fuse anymore, just delete those files. You could also consider re-installing these using brew afterwards.
To check what was modified in your Homebrew checkout, do
cd /usr/local/Library
git diff
Just reinstalled osx and only installed chrome, sublime, and xcode cli tools so far. I got these warnings from brew doctor:
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
Is it safe to remove these files or should I just ignore the warnings?
Do you, by any chance, have TrueCrypt or OSXFuse installed? Because your problem looks like this or this. The TrueCrypt problem is fixed by this script, and if you have OSXFuse, you can just remove it and use homebrew's version instead.
There's nothing wrong with the answer #Bogdan gives (I upvoted it) but in case it doesn't work for anyone, this script of mine also provides a one-shot solution--just run it, and you're good.