I updated to the latest OS, and/or restarted my computer (this happens on every major update, but this time all I did was restart my computer on 2022-09-13)
This morning I navigated to my work's codebase in the Command Line on my MacBook pro, typed in "git status" in the repository and received an error:
(IN 9/2022, this error was much different, but I didn't capture it)
xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun
git will not work!
How do I fix git, and command line tools?
The problem is that Xcode Command-line Tools needs to be updated.
** UPDATED for Ventura and updated apple dev download page **
After opening the terminal after a restart, I tried to go to my code, and do a git status, and I got an error and prompt for command line software agreement.
So press space until you get to the [agree, print, cancel] option, so careful hit space to scroll down to the end, if you blow past It you have to run a command to get it back. Use sudo xcodebuild -license to get to it again.
Just be careful on scrolling down and enter agree and press return and it will launch into an update.
Then I tried to use git after the install, and it prompted me to install Xcode tools again.
I followed my own advice from previous years (see below), and went to https://developer.apple.com/download/all/?q=Command%20Line%20Tools and downloaded
"Command Line Tools for Xcode 14" (You have to log in with your Apple ID, so have that login readily available.
You have to either download the tools from CLI or the developer page and before you can use git, you need to reboot!!! SUPER IMPORTANT, you can get stuck in a loop of downloading
Rebooting will break the loop and complete the installation of your CLI tools including git so that you can get back to work
Solutions for previous years, these may or may not be valid these days as the downloads page has changed significantly:
PREVIOUS YEARS SOLUTIONS, probably #2 is most helpful.
** Solution #1 **
Go back to your terminal and enter:
xcode-select --install
You'll then receive the following output:
xcode-select: note: install requested for command line developer tools
You will then be prompted in a window to update Xcode Command Line tools. (which may take a while)
Open a new terminal window and your development tools should be returned.
Addition: With any major or semi-major update you'll need to update the command line tools in order to get them functioning properly again. Check Xcode with any update. This goes beyond Mojave...
After that restart your terminal
Alternatively, IF that fails, and it very well might.... you'll get a pop-up box saying "Software not found on server", see below!
Solution #2
and you hit xcode-select --install and it doesn't find the software, log into Apple Developer, and install it via webpage.
Log in or sign up here:
https://developer.apple.com/download/more/
Look for: "Command Line Tools for Xcode 14.x" in the list of downloads
Then click the dmg and download.
I got some errors that the software was unavailable from the update server when trying
xcode-select --install
What fixed it for me was going here https://developer.apple.com/download/more/ and downloading Command Line Tools (macOS 10.14) for Xcode 10 and then installing it manually.
After that, the errors should be gone when you open up a new terminal.
Update for macOS Ventura 13.0.1 (Nov 2022)
Install Command Line Tools for Xcode 14.1
For me xcode-select --reset was the solution on Mojave.
In addition to dustbuster's answer I needed to set path to the Xcode folder with this command:
sudo xcode-select -switch /Library/Developer/CommandLineTools
updated from Mojave to Big Sur and got the same error :
the command
xcode-select --install
worked like a charm
After upgrade to Mac Catalina I faced the same issue, I had to run couple of commands to get this fixed.
First started with:
xcode-select --install
It didn't fix the problem, had to run the following in sudo
sudo xcode-select --reset
Then, finally got fixed after I switched and set the path explicitly for active developer directory:
sudo xcode-select -s /Library/Developer/CommandLineTools
Note: In case you have Xcode installed, you may need to specify Xcode directory in this case, it should be something like this
xcode-select -s /Applications/Xcode.app
For me what worked is the following:
sudo xcode-select --reset
Then like in #High6's answer:
sudo xcodebuild -license
This will reveal a license which I assume is some Xcode license. Scroll to the bottom using space (or the mouse) then tap agree.
This is what worked for me on MacOS Mojave v 10.14.
I've used xcode-select --install given in the accepted answer in previous major releases.
I've just upgraded to OS X 10.15 Catalina and run the Software Update tool from preferences again after the OS upgrade completed. The Xcode utilities update was available there, which also sorted the issue using git which had just output
xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools)
If you use xcode then install it (~12GB)
xcode-select --install
Otherwise install latest command line tools (~500MB)
Update: If struck in install loop
xcodebuild -runFirstLaunch
if there are several versions, select one of them from:
xcode -> Preferences and tap Locations then select, as the followng image
I figured out the Xcode Command Line Tools part from the error message, but after running Xcode and getting the prompt to install the additional tools it did claim to install them, but still I got the same error after opening a new terminal.
So I did the xcode-select --install manually and after that it worked for me.
Mac OS : Big Sur
First Priority
sudo xcode-select --reset
sudo xcodebuild -license
Second Priority
xcode-select --install
Following worked on M1
ProductName: macOS
ProductVersion: 11.2.1
BuildVersion: 20D74
% xcode-select --install
Agree the Terms and Conditions prompt, it will return following message on success.
% xcode-select: note: install requested for command line developer tools
If you have Xcode downloaded manually (i.e. not from the App Store) or don't have Xcode at all:
sudo rm -rf /Library/Developer/CommandLineTools
Go to https://developer.apple.com/download/more/ to download Command Line Tools (macOS 10.14) for Xcode 10
Setup Command Line Tools
If you have Xcode installed from the App Store:
xcode-select --install
Open Terminal:
install XCode developer tools and fix the problem.
$ xcode-select --install
Reset the path to Xcode if you have several versions:
$ xcode-select --switch /Applications/Xcode.app
$ xcode-select --switch /Library/Developer/CommandLineTools
Run this command:
xcode-select --install
Hit return for a progress indicator on the Command Line Tools download.
After installation of the Command Line Tools has been completed, your Mac should be rebooted. If you’re getting “xcrun error invalid active developer path” while working in Terminal, refresh the application or relaunch it.
Even after following the above-mentioned steps, if you see the error: invalid active developer path (/Library/Developer/CommandLineTools). The next step would be to try and install Command Line Tools using a DMG file that can be downloaded directly from the Apple website.
Again, if you are using Homebrew, you need to update it. You don’t need to uninstall and again install Homebrew on Mac.
NOTE: If you are using Homebrew, try updating it after re-installing Command Line tools.
Credits: Git not working after macOS Update
This just happened to me after upgrading my Macbook pro to macOS Ventura. After the upgrade, the git command line stopped working with showing up this message.
xcrun: error: invalid active developer path
(/Library/Developer/CommandLineTools), missing xcrun at:
/Library/Developer/CommandLineTools/usr/bin/xcrun
Running brew upgrade fixed git command line.
As of September 13, 2022, I had a similar issue after upgrading my MBP M1 to Monterey 12.6, and although I followed some of the answers, my Mac kept prompting me with a dialogue to install git as a developer tool. Every time that the installation was completed, I was prompted to the same dialogue.
Finally, I had to do a combination of all the answers to make it work:
First remove the command line tool:
sudo rm -rf /Library/Developer/CommandLineTools
Reinstall the xcode-select:
xcode-select --install
The above will prompt you with a dialogue to confirm the installation.
Set path to the Xcode folder with following:
sudo xcode-select -switch /Library/Developer/CommandLineTools
I observed in the Catalina privacy setting if Xcode not added in Full access disk I will get the same error, Xcode does not run scripts. Add your Xcode the same as in the attached image. After that clean build and run. Hope so it will work.
For me, I didn't have xcode installed (on Mojave OS). I went to the App Store on my mac and downloaded it, then went back to terminal and typed git and hit enter, then it worked.
I found that my version of Xcode was too outdated and installing command-line-tools wasn't helping. Here's what I did:
I completely uninstalled the outdated XCode
I reinstalled the most recent XCode from the app store
That was all. Git was restored.
This works for me
sudo xcode-select --reset
sudo xcodebuild -license
X-code must be installed.
For me, for the macos Ventura 13.0 user installing this software helped
I wasn't able to run any xcode install commands, git was not working at all.
You can find this package here
https://developer.apple.com/download/all/
For those using Catalina and Xcode-beta:
sudo xcode-select -s /Applications/Xcode-beta.app/Contents/Developer
I updated my macOS yesterday，from macOS Mojave（10.14.6）to macOS Catalina（10.15.7），I was executing "git" command in my project. I get same errors。
run：
xcode-select --install
After Updating macOS to Monterey (12.3) from BigSur getting such issue
only worked-
xcode-select --install
Done!
With previous app development experience, may I say with confidence that the git version delivered with apple always create problems. So the sooner you get rid of apple git the better, so may I suggest:
brew uninstall git
brew update
brew install git
# which git
/usr/local/bin/git
For me It happened after Mac OS update to Mojave and git was not functioning in Intellij
Solution:-
Go to Settings, then File | Settings | Version Control | Git and edit Path to Git executable field which is /usr/local/bin/git
I had the same issue and couldn't use SVN after the update,
Just in case if doing xcode-select --install didn't fix the issue,
You might see,
svn: error: The subversion command line tools are no longer provided by Xcode.
Refer : https://developer.apple.com/documentation/macos_release_notes/macos_catalina_10_15_release_notes
Try installing the svn by brew
brew install svn
This should get you going.
For Ventura 13.1
I updated from macOS BigSur to Ventura 13.1 (Jan 2023). I only installed Xcode on the apple store and it worked for me.
I'm attempting to get the LTS version of node installed on my machine via homebrew but I seem to be having some issues. If I run brew install node#6 to get the latest LTS version (6.10.3), everything seems to complete with no issues. Then, if I run brew list, I will see node#6 has indeed installed. BUT, if I check which version of node is installed using node -v, I receive zsh: command not found: node. I'm pretty new to homebrew and the command line in general. Where have I gone wrong?
Any help would be greatly appreciated, and I can provide more info if requested. Thanks!
For those curious, I ended up just using brew install node to install the most current version of node. Trying to install node#6 was troublesome, but it seems my struggle was pertaining to an issue where homebrew required node#6 to be linked using brew link node#6 --force. More info can be found here:
https://github.com/Homebrew/brew/issues/2220
Note that I did not try this solution.
As indicated in the GitHub issue linked above, if you run brew info node#10 (replace node#10 with your version) it provides a line to add the non-latest node version to your path:
If you need to have node#10 first in your PATH run:
echo 'export PATH="/usr/local/opt/node#10/bin:$PATH"' >> ~/.zshrc
Running echo 'export PATH="/usr/local/opt/node#10/bin:$PATH"' >> ~/.zshrc adds a line to the bottom of my .zshrc file:
export PATH="/usr/local/opt/node#10/bin:$PATH"
If you're using Bash, it'd be your .bashrc file. I'm guessing Homebrew picks up on that, but worth double checking.
This line will add /usr/local/opt/node#10/bin to my PATH when I start my terminal. I need to restart my terminal to get immediate access. Or I can re-source the .zshrc file. I only have to do this the first time:
source ~/.zshrc
Now node works. I can verify by checking the version:
node -v
# v10.17.0
Could you check if /usr/local/bin is in your $PATH? Also, maybe run brew doctor?
Our server OS is CentOS 6.8, I was trying to install google-cloud-sdk, even though I installed
python 2.7 in /usr/local/bin
, it is still looking at old version of
python 2.6 in /usr/bin
. I tried giving export PATH=/usr/local/bin:$PATH to first look at /usr/local/bin than /usr/bin but still the problem persists. please suggest a way to fix.
The way I have solved this (and I know it works) is to first install Python 2.7 in whatever way you'd like, then install pip using Python 2.7 which will give you pip2.7. You can then use pip2.7 to install the google_compute_engine module so that it ends up in the right modules folder.
# get pip2.7
wget https://bootstrap.pypa.io/get-pip.py
python2.7 get-pip.py
# install the gcloud module
pip2.7 install google_compute_engine
You can then add this to your $HOME/.bashrc
export CLOUDSDK_PYTHON=/usr/local/bin/python2.7
This is the best repeatable way I know of
Go to the google-cloud-sdk folder and open the install.sh file.
Change the CLOUDSDK_PYTHON="python" value to CLOUDSDK_PYTHON="python2.7"
Rerun the install with the command:
./install.sh
Or you could install it using yum:
https://cloud.google.com/sdk/downloads#yum
If you are on Windows This is a simple solution that worked for me:
open Powershell as administrator and run this to add your Python folder to your environment's PATH:
$env:Path += ";C:\python27_x64\"
Then re-run the command that gave you the original error. It should work fine.
Alternatively you could run that original (error-causing) command within the Cloud SDK Shell. That also worked for me.
I found a CLOUDSDK_PYTHON inside my ~/.bash_profile (or ~/.zshenv).
I removed it, and went back into my google-cloud-sdk directory and reinstalled it.
./install.sh
This fixed the issue for me.
I am using mac. I have currently installed Node.js 4.4.3
Aleeshas-MacBook-Air:~ aleesha$ node -v
v4.4.3
I want to update Node.js to it's latest version by following these steps.
First I tried to execute: brew update. However, I was getting the below error when I executed the command:
brew update Error: /usr/local is not writable. You should change the
ownership and permissions of /usr/local back to your user account:
sudo chown -R $(whoami) /usr/local
So after searching for solution on Google, I ran this command: sudo chown -R $(whoami) /usr/local
After that I again executed the brew update command. I think it was successfully executed since I didn't see any error message. Last few lines on the command prompt were:
==> Migrating HOMEBREW_REPOSITORY (please wait)...
==> Migrated HOMEBREW_REPOSITORY to /usr/local/Homebrew! Homebrew no longer needs to have ownership of /usr/local.
If you wish you can
return /usr/local to its default ownership with: sudo chown
root:wheel /usr/local Aleeshas-MacBook-Air:~ aleesha$
However after this step when I execute the upgrade command, it failed.
Aleeshas-MacBook-Air:~ aleesha$ brew upgrade node
Error: node not installed
Aleeshas-MacBook-Air:~ aleesha$
I am not sure what exactly needs to be done here.
Thanks
EDIT: Executed brew doctor to check for system anomalies.
Aleeshas-MacBook-Air:~ aleesha$ 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 and just ignore them. 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:
/Library/Frameworks/Python.framework/Versions/3.5/bin/python3-config
/Library/Frameworks/Python.framework/Versions/3.5/bin/python3.5-config
/Library/Frameworks/Python.framework/Versions/3.5/bin/python3.5m-config
Warning: No developer tools installed.
Install the Command Line Tools:
xcode-select --install
Warning: Python is installed at /Library/Frameworks/Python.framework
Homebrew only supports building against the System-provided Python or a
brewed Python. In particular, Pythons installed to /Library can interfere
with other software installs.
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/node/android-ifaddrs.h
/usr/local/include/node/ares.h
/usr/local/include/node/ares_version.h
/usr/local/include/node/libplatform/libplatform.h
/usr/local/include/node/nameser.h
/usr/local/include/node/node.h
/usr/local/include/node/node_buffer.h
You didn't install Node using Homebrew, use this gist to uninstall your current installation of Node.
And then:
brew update && brew install node
It seems like you didn't install nodejs through brew. If you installed Node without brew, brew doesn't recognize it. I had the same issue until I realised that I installed Node with Node Version Manager. Make sure you installed it using Brew.
brew list
Will show you the things brew installed.