I just upgraded from Yosemite to El Capitan (and replicated the problem upgrading from El Capitan to Sierra), and when I try to type for example git status inside a terminal, I get the following error:
xcrun: error: invalid active developer path
(/Library/Developer/CommandLineTools), missing xcrun at:
/Library/Developer/CommandLineTools/usr/bin/xcrun
I don't have Xcode installed, never did.
Anyone have a solution?
Found the fix for the problem here.
xcode-select --install
This will bring up a prompt to install the necessary command line tools.
If you have issues with the xcode-select --install command; e.g. I kept getting a network problem timeout, then try downloading the dmg at developer.apple.com/downloads (Command line tools OS X 10.11) for Xcode 7.1
In macOS 10.14 this issue may also occur if you have two or more versions installed. If you like xCode GUI you can do it by going into preferences - CMD + ,, selecting Locations tab and choosing version of Command Line Tools. Please refer to the attached print screen.
I tried the solution xcode-select --install but it don't help me, I update from Sierra to High and happened this, my solution:
sudo xcode-select --reset
Reassigning the path Xcode is configured with worked for me.
sudo xcode-select -switch /Applications/Xcode.app
You'll then likely be prompted (after trying a command) to agree to the license agreement.
I had the same issue after upgrading to macOS Catalina.
This didn't work for me:
xcode-select --install
Downloading and installing Command Line Tools for Xcode 12 did it!
For me, after I've removed Xcode, I have to switch active developer path as follows:
sudo xcode-select -s /
I just updated to High Sierra and I couldn't just run xcode-select --install. First, I had to actually install xcode from the app store. Then I ran xcode-select --install. Then I had to run sudo xcodebuild -license, agree to the terms, then I could finally run git commands again.
Updated to High Sierra 10.13.2
xcode-select --install ALONE did not work for me.
Download X-code from app store
$xcode-select --install
a. May need to update after install using softwareupdate in command line. $sudo softwareupdate -i "Command Line Tools (macOS High Sierra version 10.13) for Xcode-9.1"
$sudo xcodebuild -license
For Mojave
Uninstall Any old version of Command Line Tools:
sudo rm -rf /Library/Developer/CommandLineTools
Download and Install Command Line Tools 10.14 Mojave.
For those also having issues with heroku command line tools after upgrading, I also had to do the following in my terminal:
xcode-select --install
brew install heroku/brew/heroku
brew link --overwrite heroku
It seems the upgrade to High Sierra messed with my symlinks in addition to forcing me to reinstall xcode tools. I kept getting 'not a directory' errors:
▸ stat /Users/mattymc/.local/share/heroku/client/bin/heroku: not a directory
▸ fork/exec /Users/mattmcinnis/.local/share/heroku/client/bin/heroku: not a directory
Hope that saves someone an hour :)
After update to macOS 10.13.3
After updating do macOS 10.13, I had to install
"Command Line Tools (macOS 10.13) for Xcode 9.3"
downloaded from https://developer.apple.com/download/more/
I upgraded mac os to macOS High Sierra - 10.13.3 and faced a similar issue while trying to install watchman (with command - brew install watchman).
ran the command: xcode-select --install, then ran "brew install watchman" - Everything works fine!
For the most recent version Mojave version 10.14.1, I use
solved by downloaded from https://developer.apple.com/download/more/ " login by apple id, and download
Command line tool newest stable version.dmg
That makes everything work
the old answer
xcode-select --install
doesn't work for me.
sudo xcode-select -s /Applications/Xcode-beta.app/Contents/Developer
Work for me.
Even if you do xcode-select --install it was not fixing that for me as it showed some network error. The problem was that it could not connect to the app store. I did the following to fix it.
Open keystore
Go to system root and select certificates.
Open digicert high assurance EV.
Expand the trust section, mark it as never trust.
Restart system now repeat step 1, 2, 3. and mark the trust policy as
back to use system defaults.
Your app store should work now and you should be able to run xcode-select --install
Related
Has anyone with macOS 13 (Ventura) managed to install MongoDB? Getting the following error:
==> Installing mongodb-community#5.0 from mongodb/brew
Error: Your Command Line Tools (CLT) does not support macOS 13.
It is either outdated or was modified.
Please update your Command Line Tools (CLT) or delete it if no updates are available.
Update them from Software Update in System Preferences or run:
softwareupdate --all --install --force
If that doesn't show you any updates, run:
sudo rm -rf /Library/Developer/CommandLineTools
sudo xcode-select --install
Alternatively, manually download them from:
https://developer.apple.com/download/all/.
You should download the Command Line Tools for Xcode 14.1.
Reinstalled the Command Line Tools for Xcode 14.1, but still getting the same error.
I followed the instructions on MongoDB's site: https://www.mongodb.com/docs/manual/tutorial/install-mongodb-on-os-x/
Ideally I need 5.0 for a project, but I've also tried installing 6.0 and the same error occurs.
The following steps should fix the issue. I had the same issue.
Uninstall the existing CLT
sudo rm -rf /Library/Developer/CommandLineTools
Download the Command Line Tools for Xcode 14.1 Release Candidate 2 (latest as of writing) from here: https://developer.apple.com/download/all/?q=Command%20Line%20Tools%20for%20Xcode
Install the downloaded package
brew upgrade
And then retry installing MongoDB and the installation should pass through.
I've just upgraded to Mojave and am trying to install phalcon, it was smooth installation with standard compile installation on macOS previous version (High Sierra),
git clone git://github.com/phalcon/cphalcon.git
cd cphalcon/build
sudo ./install
with Mojave, it gives follow error.
In file included from /usr/include/php/ext/spl/spl_iterators.h:27:
/usr/include/php/ext/pcre/php_pcre.h:29:10: fatal error: 'pcre.h' file not found
#include "pcre.h"
^~~~~~~~
1 error generated.
make: *** [phalcon.lo] Error 1
anyone encounter the same problem? it would be good to know how to get it solved.
Thanks
OK after a few trying, this is what I do to fix it, hope it would help for someone else.
Go to https://www.pcre.org/ and download latest pcre, more specifically,
tar -xzvf pcre-8.42.tar.gz
cd pcre-8.42
./configure --prefix=/usr/local/pcre-8.42
make
make install
ln -s /usr/local/pcre-8.42 /usr/sbin/pcre
ln -s /usr/local/pcre-8.42/include/pcre.h /usr/include/pcre.h
and it went through.
I have Mojave on my Mac, and i installed Phalcon into my Mac through HomeBrew, step by step
1/Install php through brew (with correct version)
2/Install phalcon through brew
Hope it can help you
As many have pointed out this should work, xcode-select --install
I however consistently get
I have XCODE Version 5.0.1 (5A2053) installed.
What am i missing please and how can I get command line tools installed?
I am trying to install homebrew according to the guidelines described in here.
I have curl and rvm, and want to install rails 1.9.3 on my lion 1.7.4 with Xcode 4.3.2 and with developer command line tools installed.
It seems I will need libksba, which requires me to use to command brew install libksba.
So I will need Home Brew.
I follow the instructions and use
/usr/bin/ruby -e "$(/usr/bin/curl -fsSL https://raw.github.com/mxcl/homebrew/master/Library/Contributions/install_homebrew.rb)"
which outputs the following:
$ /usr/bin/ruby -e "$(/usr/bin/curl -fsSL https://raw.github.com/mxcl/homebrew/master/Library/Contributions/install_homebrew.rb)"
==> This script will install:
/usr/local/bin/brew
/usr/local/Library/Formula/...
/usr/local/Library/Homebrew/...
Press enter to continue
==> Downloading and Installing Homebrew...
==> Installation successful!
You should run `brew doctor' *before* you install anything.
Now type: brew help
[~]$
[~]$
[~]$ brew doctor
/usr/local/Library/Homebrew/tab.rb:1:in `require': no such file to load -- ostruct `(LoadError)`
from /usr/local/Library/Homebrew/tab.rb:1
from /usr/local/Library/Homebrew/bottles.rb:1:in `require'
from /usr/local/Library/Homebrew/bottles.rb:1
from /usr/local/Library/Homebrew/extend/pathname.rb:2:in `require'
from /usr/local/Library/Homebrew/extend/pathname.rb:2
from /usr/local/Library/Homebrew/global.rb:1:in `require'
from /usr/local/Library/Homebrew/global.rb:1
from /usr/local/bin/brew:10:in `require'
from /usr/local/bin/brew:10
[~]$
So this means basically that brew was not installed right. Do I have to change the path at which it is looking for? I used to have MacPorts in, which I completely erased so there should be no conflicts there. Please help!!! Thanks a lot! It's an awesome community.
UPDATE:
I time machined back a year because I thought I did something critically wrong. Now I still have an issue installing, but it seems a bit more common.
I installed homebrew using
/usr/bin/ruby -e "$(/usr/bin/curl -fsSL https://raw.github.com/mxcl/homebrew/master/Library/Contributions/install_homebrew.rb)"
Any command of "brew" gives me this error:
[~]$ brew
/usr/local/bin/brew:6:in `require': no such file to load -- pathname (LoadError)
from /usr/local/bin/brew:6
Any suggestions? Thank you all!
I had the same problem as mentioned in my comment above. To resolve it I ended up having to restore my default system ruby. I am on SnowLeopard - OSX 10.6.8, so your resources may vary, but what I did was:
uninstall xcode: sudo /Developer/Library/uninstall-devtools --mode=all
rsync or copy /System/Library/Frameworks/Ruby.framework from another machine running 10.6.8
You also need the ruby executables in /usr/bin to point to the system Ruby: /usr/bin/{erb,gem,irb,rdoc,ri,ruby,testrb}
these are just symlinks to /System/Library/Frameworks/Ruby.framework
erb -> ../../System/Library/Frameworks/Ruby.framework/Versions/Current/usr/bin/erb
so I re-symlinked them, for example from /usr/bin: sudo ln -s ../../System/Library/Frameworks/Ruby.framework/Versions/Current/usr/bin/erb ./erb
the brew executable currently uses /usr/bin/ruby so that needs to be there in the least
I hear future versions of brew will point directly at the system ruby on the /System/Library/Frameworks/Ruby.framework path, so symlinking ruby to a custom install is a bad idea
At this point brew commands worked again and ostruct (part of ruby standard lib) was again found. I went ahead and added xcode back in and worked through some minor 'brew doctor' errors.
I have now replaced all my old macports packages with homebrew packages and its such an improvement!
I have installed everything like I was told to by the android website and all I keep getting after I create my avd is
"Failed to start emulator: Cannot run program "/home/christopher/Desktop/android-sdk-linux_86//tools/emulator": java.io.IOException: error=2, No such file or directory".
Anybody got any ideas??? I'm running linux if that helps.
If you're running a 64-bit system, you need to install ia32-libs:
sudo apt-get install ia32-libs
If you are running Ubuntu 13.10 x64 or the latest Linux Mint x64 then the ia32-libs package is not available anymore. The solution which worked for me without any problems is to:
sudo apt-get install libc6-i386 lib32stdc++6 lib32gcc1 lib32ncurses5 lib32z1
Hope this will help!
It's a lib32 problem, you need to install getlibs (http://frozenfox.freehostia.com/cappy/getlibs-all.deb) and run it against applications that do not work (e.g., adb and emulator).
cmd from first comment didn't worked for me (Crunchbang linux) so I solved this problem with
sudo aptitude install ia32-libs lib32ncurses5 lib32stdc++6
In directory tools, there are many types of emulator, while my computer works with emulator64-arm! My system is Linux Mint 16 amd64! Good luck!
./emulator64-arm #yxphone -sdcard yxsd -scale 0.8
Another alternative to that, and one in which you will not need to add archs or install anything, is going to the android-sdk install directory, and then to tools dir. There you'll find the emulator executable and plenty other emulator executables too.
Since the emulator file seems to actually be a chooser to which one of the others it will launch based on your OS arch (the problem is that the file itself is a 32bit executable), you can just rename it to emulator.old or something and then make a symlink named emulator to the correct file (mine was emulator64-x86 for amd64 arch). So...
cd (...)/android-sdk/tools/
mv emulator emulator.old
ln -s emulator64-x86 emulator
And it should work! The downside for this is that you'll probably have to do it everytime you update the SDK Tools and also will only fix the emulator, adb and some other tools will have the same problem! Anyways, still an alternative!
64-bit system needs to install ia32-libs and it is working with latest Linux Mint 16 Cinnamon. I have used this. Just run Commands in terminal
sudo apt-get install ia32-libs
sudo apt-get update
Try this, for me work fine
sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install libncurses5:i386 libstdc++6:i386 zlib1g:i386