Clean Mavericks Install: "Warning: No developer tools installed."

[cbfullerx]

Reformatted drive, installed Mavericks (i.e. clean install), installed Xcode via App Store (which includes the developer tools), then installed Homebrew.

Homebrew reports:

$ brew doctor
Warning: No developer tools installed.
You should install the Command Line Tools.
Run `xcode-select --install` to install them.

The developer tools are definitely included with Xcode though. I confirmed that compiles work by installing rbenv and ruby-build via Homebrew and then installed a ruby which compiled just fine.

As far as I can tell all Homebrew features are working, it just continually complains "No developer tools installed"

Please let me know if you need further information.

[tml]

Did you try running the "xcode-select --install"?

I saw a similar problem on my Mavericks reinstall machine until I ran the suggested "xcode-select --install", which popped up some EULA box and then everything seemed to work; I'm guessing there's some switch that didn't get flipped when we installed XCode, and that homebrew is relying on that switch.

[cbfullerx]

Thanks for the quick reply. I would think that installing a new copy of the developer tools would fix the issue. But I am hoping to help troubleshoot this issue from the Homebrew end of things (on this new "clean" install that definitely already has the developer tools). If there is anything else I should try or would like me to test, please let me know how I can help.

[MikeMcQuaid]

Xcode.app does not install working developer tools currently.

[MikeMcQuaid]

To clarify: they work for some things but break for others.

[tml]

The suggested "xcode-select --install" seems to have everything working OK here for me; is there a list of what's known to be broken?

[MikeMcQuaid]

xcode-select --install will fix all issues, yes.

[cbfullerx]

Okay, thanks for the responses. Can you please clarify what is broken before running that command? In other words, I have not run that command yet and my compiles are working fine. It's only the "No developer tools installed" warning that Homebrew shows. Other than that I have not experienced any issues. So can you please elaborate on the "break for others" comment? Also, can you please confirm if running that command will install a new copy of the dev tools or simply fixes up the dev tools that are already installed with Xcode. Thanks!

[adamv]

Some software, which we have not compiled a list of, will fail to build without the CLT. If you search "xcode-select" in closed issues, some of them will come up.

[cbfullerx]

Ok, will do. And does "xcode-select --install" actually install a second copy of the dev tools or does it simply fix up the one included with Xcode?

[MikeMcQuaid]

It installs more stuff but I'm unsure whether it's a full second copy. Not much we can do about it I'm afraid. Apple are aware.

[cbfullerx]

Okay, thanks everyone. Sorry for bringing this up again. Really appreciate it through!

[cbfullerx]

Even though I searched previous issues before posting my question, I clearly missed a lot of relevant info. Here's a related issue for example:

#23731

Thanks again everyone.

[cbfullerx]

Just a thought. If it helps, I can leave my system as it is, without running "xcode-select --install" and am happy to test again later. Such as when there is an Xcode update released. And I searched for "xcode-select" in closed issues as @adamv suggested but was not sure which one would be an ideal test. But if there is a specific package I should test with, please let me know which. So I can try installing it now, see it fail, and then try again after the next Xcode update. Please let me know if this would be helpful.

[MikeMcQuaid]

tuntap is one: #23487

[cbfullerx]

I assume that means it's helpful. So, ok, I just tested installing tuntap and failed for me. I'll wait till next Xcode update and test installing tuntap again. Will report results here.

[MikeMcQuaid]

@cbfullerx yeh, thanks.

[conradwt]

Using Xcode 5, there's no separate download or install for the CLT. Xcode 5 now includes everything that you'll need for development in both the command line as well as the Xcode IDE. Thus, the "xcode-select --install" is not required after you have downloaded Xcode 5 from the App Store. In its current implementation "xcode-select --install" will attempt to install things again. Just make sure that "xcode-select --print-path" points to the correct Xcode installation. For example, the default path should be something similar to the following:

$ xcode-select --print-path
/Applications/Xcode.app/Contents/Developer

[cbfullerx]

That all seems correct to me. And in fact that's exactly why I opened this case. However, not only does Homebrew complain that there are no dev tools, certain packages fail to install. (And xcode-select --install has simply been utilized by others as a means to move ahead and install troublesome packages) So my plan is to wait for an Xcode update and then attempt installing tuntap again. (That's just one of the packages that fails to install) and I'll report back here. In the meantime, the other packages I use like rbenv and ruby-build install fine and ruby compiles without issue too. (BTW my xcode-select -p reports the correct path). I am just avoiding the install step for now so I can troubleshoot and see if the next Xcode update solves this issue.

[MikeMcQuaid]

@conradwt That's not the case; Xcode.app has some headers in wrong/incorrect locations which break builds. Some stuff may work with Xcode-only but there's enough issues that we're recommending people install the CLT. Feel free to not do so at your own risk but please don't advise others to do so.

[conradwt]

@MikeMcQuaid Which headers are in the wrong place? Also, has this issue(s) been filed at bugreporter.apple.com? I understand that people would like to move forward with their package installation(s) by installing standalone CLT but if there's something wrong with CLT which is shipped with Xcode 5 GM, then I would highly recommend reporting it to Apple where it can be addressed.

@cbfullerx If you have a developer.apple.com, you can try the next GM seed release of Xcode 5.

[MikeMcQuaid]

@conradwt It has been reported to Apple. For more details read above and linked issues.

[cbfullerx]

FYI, I updated Xcode to 5.0.2 and same issue exists. i.e. Homebrew still complains there's no dev tools. And my example test install of tuntap failed with the same error as before.

[tftio]

Is there a Radar for this problem?

[MikeMcQuaid]

@cbfullerx Thanks for testing. The warning will always be there on 10.9 until we turn it off. Shame tuntap failed.
@jfb I don't know. Apple are aware.

[robeson]

FYI (fresh Mavericks), I couldn't get past the install prompt from "Install Command Line Developers Tools" installer app. It just did nothing after I clicked "Install". However, once I moved my Terminal out of Full Screen mode, it worked fine. Strange case, yes, but maybe this'll help someone with the same issue - maybe.

[JustinTArthur]

I'm curious, because on one environment, I don't think I had this problem. Is it possible that it only occurs if you upgrade to Mavericks after the installation of XCode 5? In the environment that had the working command line tools, I believe I held off on the XCode upgrade until after the Mavericks upgrade.

[cbfullerx]

@JustinTArthur fyi, this thread is regarding a clean fresh new install of Mavericks and then a fresh new install of Xcode, not upgrades. And specifically about how the new Xcode includes the dev tools, but the included dev tools have issues that prevent some software from compiling, unless of course you manually run the installer via "xcode-select --install". I will report back on this thread if a future version of Xcode has a working dev tools included that does not require the manual dev tools installation.

[luiscvega]

My apologies but this might be OT:

Can I install Homebrew without installing Xcode? If yes, can I just download CLT from the Apple Developer website? (I'm about to do a clean install of Mavericks.)

[mistydemeo]

@luiscvega You don't even need the Apple developer website - you can xcode-select --install at the terminal to install the CLT.

[tigris]

@mistydemeo FYI, the xcode-select --install command currently fails at all times (tried on multiple mavericks installs), due to "network error". I suspect it's an xcode issue, perhaps the HTTP location it is hard coded to download said tools from is no longer active. In any case, the correct solution to install the most up to date CLT for xcode in mavericks is to do this https://discussions.apple.com/message/23548005#23548005

There are many issues in this repo, and S/O questions where xcode-select --install is the supposed answer (not to mention in the message from brew doctor itself), which is frustrating because it's (currently) completely misleading.

[conradwt]

@tigris I believe the following post clarifies many of the issues:

https://devforums.apple.com/message/918937#918937

Next, I noticed that a few brew packages had hardcoded paths to header files which would cause them to fail under OS X 10.9 with Xcode 5. Thus, the CLT can be used to assist those packages that have not been properly upgraded for OS X 10.9. Again, I haven't had the need to install the CLT using xcode-select --install.

[tigris]

@conradwt my point was simply that homebrew telling you to run xcode-select --install when it doesn't even work is IMO a bug, and finding the correct solution was no easy feat. I feel it should be documented somewhere.

[unphased]

Is this Warning: No developer tools installed. You should install the Command Line Tools. Run 'xcode-select --install' to install them. something that I am supposed to just ignore forever now that I am on 10.9? Why can't you put in a conditional switch to not display it (when on 10.9)?

[tml]

I'm on 10.9 and am not running into this issue at the moment. Have you followed the steps outlined in the previous few comments?

[unphased]

When I first ran xcode-select --install, it just sort of sat there for an hour and didn't do much. When the loading/install bar finally went away, nothing changed.

But today, when I ran it, it completed within a reasonable amount of time (2 minutes), and now brew is no longer giving me this warning.

I guess that has me feeling a little better. But not all that much. Anyway. As long as stuff continues to work when I bang it a few times (note also that while I was getting that warning, stuff did continue to work), I can get away without reinstalling. Huzzah.

[cbfullerx]

I just happened by this old issue and thought I'd leave a final follow-up comment.

Since there are such a large number of off topic comments on this thread, please look back to the original question at the top to get clarity on the specific issue I wanted to address.

I am no longer running Mavericks, but I thought I'd follow up with the following info:

After reformatting drive, installing Yosemite (i.e. clean install), installing Xcode via App Store (which includes the developer tools), and then installing Homebrew, there is no reason to execute xcode-select --install. And brew doctor does not complain.

I have not had any issues with installing packages that I am interested in. (I was not able to test tuntap, which was the test I was previously using for Mavericks, since that's not ideal for Yosemite due to kext changes).

In summary, the specific issue that I originally opened should definitely be closed. Thanks for everyone's help on this. Especially @MikeMcQuaid. Cheers.