Skip to content
This repository has been archived by the owner on Feb 1, 2018. It is now read-only.

Troubleshooting

Jump to bottom
Shaun Jackman edited this page Jul 12, 2014 · 39 revisions

Troubleshooting Linuxbrew

If you can reproduce your issue by compiling the software package outside of Homebrew/Linuxbrew, please report your issue to that project's maintainers.

Linuxbrew is a fork of Homebrew. If you believe your issue is specific to Linux, please report your issue to Linuxbrew. If you believe your issue is specific to Homebrew but not specific to Linux, please report your issue to Homebrew.

Please install the dependencies of Linuxbrew using your distribution's native package manager.

Troubleshooting Homebrew

PLEASE,
PLEASE,
PLEASE run brew update and brew doctor BEFORE CREATING AN ISSUE!

If you create an issue, please copy the output of running

  • brew --config
  • brew doctor
  • brew install -v <formula name> 2>&1

and paste it into a Gist, and provide a link to this gist in your issue.

Thank you!

1) Check for Common Issues

  • Run brew update — then try again.
  • Run brew doctor — the doctor diagnoses common issues.
  • Try using the old environment, e.g. run brew install --env=std graphviz.
  • If you’re installing something Java-related, maybe you need the Java Developer Update?
  • Check that Command Line Tools for Xcode (CLT) and/or Xcode are up to date.
  • If things fail with permissions errors you should check the permissions in /usr/local. If you’re unsure what to do, you can:
sudo chown -R $(whoami) /usr/local

But really you should know what you’re doing.

* brew --config will list these versions. If you have Xcode installed, check the App Store for upgrades and in Preferences for CLT upgrades. If you only have the CLT installed, then check Apple Connect.

Listen to Dr. Brew

  • Update your Xcode and Command Line Tools for Xcode! Make sure that Xcode is up-to-date in the App Store. Check the CLT package is up-to-date (either via Xcode, Preferences or at Apple Connect).
  • If brew doctor warns about unbrewed dylibs, these seriously cause build trouble. Yes, we know it’s hard to know what to do with this warning. But it’s hard to advise!
  • If brew doctor tells you to reinstall Xcode. If you have Xcode 4.3 or later, and clang --version returns an outdated version, but xcrun clang --version returns a newer. Then you'll need to reinstall Command Line Tools. Uninstall using remove_CLI_tools.sh script, reopen Xcode and you should be able to install Command Line Tools again. Finally, clang --version should show the correct version.

2) File a Ticket for the Bug

We’ll fix the bug if you ticket it. In the following instructions replace <formula name> with the name of the formula that failed to build.

  1. Create a new ticket. If the formula comes from another tap, like josegonzalez/php or homebrew/dupes, please create a ticket there;
  2. Title it “<formula name> failed to build on 10.x”, where 10.x is your version of OS X;
  3. Upload relevant debugging information by either:
  • Manually creating a new Gist, that contains the following:
    1. The output from HOMEBREW_MAKE_JOBS=1 brew install -v <formula name> 2>&1,
    2. The contents of the largest numbered log in ~/Library/Logs/Homebrew/<formula name>, e.g. 03.make,
    3. The output from brew doctor, and
    4. The output from brew --config.
  • Alternatively, use brew gist-logs --config --doctor <formula name>.
  1. Link to the gist in your ticket. Be sure to post the https: link from the browser bar and not the git: link.

Thank you!

Clone this wiki locally