XCode and git are fighting. "no developer tools were found"

Question

Level 1

89 points

XCode and git are fighting. "no developer tools were found"

Hello, my install of git is broken, and it looks like somehow my Developer tools are broken. When I try to run git, I get this error:

Agreeing to the Xcode/iOS license requires admin privileges, please re-run as root via sudo.

I have run XCode and agreed to the license. I tried running xcode-select --install and got another error:

cook47-a@rcmac (current_projects): sudo xcode-select --install

Password:

xcode-select: error: no developer tools were found, and no install could be requested (perhaps no UI is present), please install manually from 'developer.apple.com'.

After googling this error, I downloaded the commandlinetools installer from Apple for my OS (10.9.5) and XCode (6.2) versions. It installed successfully. However, git still is broken and xcode-select --install still gives the same errors.

I also tried xcodebuild -license and it does prompt me to agree to the agreement but after agreeing, no change. Still broken. Sigh

This has me completely stumped. This was working yesterday! I work in a government environment where it's possible an update changed something, so I cannot be sure exactly what might have changed.

Anyone know how I can get git working again? I tried nuking and reinstalling XCode and the Command Line tools but to no avail. git from MacPorts and /usr/bin/git are both giving the same error message.

PowerMac, OS X Mavericks (10.9.5), My work computer

Posted on Sep 17, 2015 3:58 PM

Reply

Answer 1

VikingOSX

Level 10

125,374 points

Sep 18, 2015 8:46 AM in response to wealthychef

When you initially run Xcode, you have to agree to the licence, and then it asked you to allow it to install additional stuff. I agreed to the additional Xcode installation bits, and after installing the compatible command-line tools, everything worked just fine without having to run any xcode-select, or xcrun commands.

Reply

Answer 2

wealthychef Author

Level 1

89 points

Sep 17, 2015 5:48 PM in response to VikingOSX

I'm glad it's working for you, but it's not for me. I'm asking for suggestions as to how to fix it. Is there such a suggestion somehow implicit in your comment?

Reply

Answer 3

VikingOSX

Level 10

125,374 points

Sep 18, 2015 8:46 AM in response to wealthychef

I have no idea why your installation of Xcode 6.2 and related compatible command-line tools do not work for you. What I haven't confirmed from you yet is if you agreed to allow Xcode to finish its install directly after you agreed to its licensing terms. If you were in a hurry and skipped that step, that may be the reason it isn't working for you.

Does xcrun git --version behave as your MacPorts and command-line tool (/usr/bin/git) do? Could the git repository have been moved, changed, or damaged?

I use the Anaconda Python syntax checker within Sublime Text 3. Yesterday, a normal push of an update from the developer blew up when attempting to access git. This is a first as my Xcode 6.2/Command-Line tools have been rock solid in Mavericks since they were released.

Reply

Answer 4

wealthychef Author

Level 1

89 points

Sep 17, 2015 8:36 PM in response to VikingOSX

I believe I allowed XCode to do everything it wanted to do, and searching through the preference panes etc. did not reveal any missing installs or unfinished business that I know how to discover. I simply agreed to license terms, an install process of some sort did happen, and then nothing changed with git, which still complains that XCode is unhappy.

The git repo is unchanged, so it's not git-related per se.

I'm going to have to run the xcrun git --version command tomorrow at work as I also seem to be having trouble getting to my work machine. :-( When it rains, it pours I guess! However, as I recall, git --version is working fine, it's only "real" commands such as "git pull" that are failing.

thanks for the questions. This is a very weird problem. I can't find anyone else out there reporting the same issue, which disturbs me.

Reply

Answer 5

VikingOSX

Level 10

125,374 points

Sep 18, 2015 5:58 AM in response to wealthychef

As it turns out, I solved that git pull --ff syntax error in my sublime text anaconda package by simply changing the current Python from 3.5.0 to the default Mavericks 2.7.5 version. I only use the git installed by the command-line tools (v1.9.5).

As it turns out, Apple has several Python scripts inside Xcode.app/Contents/SharedFrameworks/LLDB.framework. These scripts expect Python 2.7.5. If you have used a package manager to install a release of Python 3 as your default Python, it may be worth using the default OS X Python while attempting to perform a git pull request to see if this is the incredible reason for your git issues.

Reply

Answer 6

wealthychef Author

Level 1

89 points

Sep 18, 2015 8:36 AM in response to VikingOSX

I'm using the system python at /usr/bin/python, which is Python 2.7.5

cook47@rcmac (RC_bash_lib (master)): type python

python is /usr/bin/python

cook47@rcmac (RC_bash_lib (master)): python --version

Python 2.7.5

"xcrun git pull" fails in the same way as plain old "git pull" does.

Reply

Answer 7

wealthychef Author

Level 1

89 points

Sep 18, 2015 8:46 AM in response to wealthychef

OK, I found the problem: the message was coming from the *remote git server*, not the client side. I ran `sudo xcodebuild -license` on the server side (where the repo is located and the git server is running) and the problem went away. Sigh.

Reply