Skip to content

Instantly share code, notes, and snippets.

@ruckus
Created September 23, 2011 18:25
Show Gist options
  • Select an option

  • Save ruckus/1238099 to your computer and use it in GitHub Desktop.

Select an option

Save ruckus/1238099 to your computer and use it in GitHub Desktop.
[codyc:php-5.3.6]$ brew doctor
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/libestr.0.dylib
/usr/local/lib/libfreetype.6.dylib
/usr/local/lib/libhiredis.dylib
/usr/local/lib/libmcrypt.4.4.8.dylib
/usr/local/lib/libzmq.1.dylib
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/libestr.a
/usr/local/lib/libfreetype.a
/usr/local/lib/libhiredis.a
/usr/local/lib/libsphinxclient.a
/usr/local/lib/libzmq.a
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/freetype2.pc
/usr/local/lib/pkgconfig/libestr.pc
/usr/local/lib/pkgconfig/libzmq.pc
/usr/local/lib/pkgconfig/nodejs.pc
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/libestr.la
/usr/local/lib/libfreetype.la
/usr/local/lib/libmcrypt.la
/usr/local/lib/libsphinxclient.la
/usr/local/lib/libzmq.la
We couldn't detect gcc 4.0.x. Some formulae require this compiler.
/usr/local/include isn't writable.
This can happen if you "sudo make install" software that isn't managed
by Homebrew.
If a brew tries to write a header file to this folder, the install will\nfail during the link step.
You should probably `chown` /usr/local/include
/usr/local/etc isn't writable.
This can happen if you "sudo make install" software that isn't managed
by Homebrew.
If a brew tries to write a file to this folder, the install will\nfail during the link step.
You should probably `chown` /usr/local/etc
Some folders in /usr/local/share/man aren't writable.
This can happen if you "sudo make install" software that isn't managed
by Homebrew. If a brew tries to add locale information to one of these
folders, then the install will fail during the link step.
You should probably `chown` them:
/usr/local/share/man/man3
/usr/local/share/man/man4
/usr/local/share/man/man5
/usr/local/share/man/man7
/usr/local/share/man/man8
/usr/bin is in your PATH before Homebrew's bin. This means that system-
provided programs will be used before Homebrew-provided ones. This is an
issue if you install, for instance, Python.
Consider editing your .bashrc to put:
/usr/local/bin
ahead of /usr/bin in your $PATH.
Some brews install binaries to sbin instead of bin, but Homebrew's
sbin was not found in your path.
Consider editing your .bashrc to add:
/usr/local/sbin
to $PATH.
/usr/local/lib/pkgconfig isn't writable.
This can happen if you "sudo make install" software that isn't managed
by Homebrew.
If a brew tries to write a .pc file to this folder, the install will\nfail during the link step.
You should probably `chown` /usr/local/lib/pkgconfig
Some "config" scripts were found in your path, but not in system or Homebrew folders.
`./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.
/usr/local/php5/bin
php-config
$GREP_OPTIONS was set to "--color=auto".
Having $GREP_OPTIONS set can cause CMake builds to fail.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment