There are several such binary installers, but the one with the most recent version of Git is git-2.3.5-intel-universal-snow-leopard.dmg. So for 10.8, you'll want to download any binary installer that ends with the name -snow-leopard.
If you look at where the binary files are actually hosted, on SourceForge, there is an a FAQ about which version of the binary installer to download if you have an older version of Mac OS X/macOS: However, as points out, as of July 2017, the binaries on the download page of the Git website are for 10.9 or newer. An OSX Git installer is maintained and available for download at the Git website, at. On Mavericks (10.9) or above you can do this simply by trying to run git from the Terminal the very first time.
The easiest is probably to install the Xcode Command Line Tools. There are several ways to install Git on a Mac. See also the Getting Started - Installing Git of the git website. When you see an install prompt, click on Yes: Agree to the GNU license terms: Select the directory you want Git to be installed in or use the default location: Select the components that you want to install. Double click on a recent version of Git to download Git for Windows. If you want a more up to date version, you can also install it via a binary installer. There is a binary installer that you can download. Navigate to the Git website’s Download page.
If you don’t have it installed already, it will prompt you to install it. See also the Getting Started - Installing Git of the git website:
You should not have to install Homebrew again or remove it and then reinstall it, a simple update should do the trick.ĭid this work to resolve your issues with git, pip, Homebrew, or whatever was triggering the xcrun error message at the command line on your Mac? Did you find another solution? Share your thoughts and experiences in the comments.There is a binary installer that you can download. This release is a snapshot of the latest FlightGear source (git version), and it might have some major bugs. Development snapshot (Latest snapshot pulled from git) - Jun-02-2011 IMPORTANT NOTICE IN USE OF DEVELOPMENT SNAPSHOT. Clicking FlightGear-2.6.0-r319.dmg will start downloading it.
You will need an Apple ID to access the download, then just head to and download Command Line Tools for Xcode (latest version) and install it manually.Īgain, Homebrew users will want to update Homebrew. Sourceforge FlightGear Mac OS X download page. If you installed or reinstalled command line tools through Terminal, rebooted the Mac, and you’re still getting the error, you can also try to manually install Command Line Tools by using a DMG file directly from Apple. Still seeing xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools)? If you are using Homebrew, you should also be sure to update Homebrew after you have (re)installed Command Line Tools. Once the installation of Command Line Tools has completed, you should reboot the Mac (sometimes simply refreshing, relaunching Terminal, or opening a new Terminal may resolve the ‘xcrun error invalid active developer path’ message too, but a reboot is recommended). Hitting return will cause a pop-up to appear with a progress indicator on the download for Command Line Tools. Installing/reinstalling CLT can be done from the command line by issuing the following command string in Terminal: Yes, even if you already have command line tools installed, you should reinstall it to resolve the error message, particularly if you are only experiencing the error after a system software update (eg, from Mojave to Monterey). The solution, as you may have guessed from the error message itself, is to reinstall or install Command Line Tools. Xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun Fix “xcrun: error: invalid active developer path” Error in Terminal on MacOS
Fortunately it’s easy to fix the “xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools)” error message, and get git, pip, Homebrew, or whatever other command line tool that failed, to start working again.įor what it’s worth, the full error message is: