With an install of RStudio, certain packages bring up issues that states "the x command requires the command line developer tools. Would you like to install them now" and when "install" is clicked, then it states there is no software to download. Any insights?
Related
I downloaded Xcode 10.2 beta from https://developer.apple.com/download/, unzipped it and moved to the applications folder. I also downloaded "Additional Tools for Xcode 10.2 beta" and "Command Line Tools (MacOS 10.14) for Xcode 10.2 beta" from https://developer.apple.com/download/more/.
Note: This is on a clean install of macOS Mojave 10.14.3
Installation of Additional Tools for Xcode 10.2 beta
I double clicked the "Additional Tools" dmg and it simply opened a Finder window. No installation, just folders with the tools (Audio, Graphics, Hardware, Utilities) and a couple of PDFs. So, I opened the Xcode-beta app and had it automatically trigger the additional tools installation.
Question #1: Is it safe to assume that Xcode-beta would only install the additional tools version that is for 10.2 beta (same as the dmg's version that I downloaded) and not the latest non-beta version?
After Xcode-beta completed installing the additional tools, there was no sign that folders like the ones that appear in the "Additional Tools" dmg had been installed in any directory anywhere.
Question #2 (two parter): (1) If the folders like the ones from the dmg don't appear anywhere after the Xcode-beta triggered installation, what did Xcode-beta install and (2) is there a difference between the additional tools Xcode-beta installs and the additional tools that are on the dmg?
Based on researching installation of Xcode Additional Tools, I tried, after Xcode-beta did its installation, dragging the folders from the "Additional Tools" dmg to the Xcode-beta/Contents/Applications folder (not Xcode-beta/Contents/Developer/Applications). When I ran Xcode-beta after doing this, these folders did appear under the Xcode > Open Developer Tool menu selection, but just the folders, no navigation hierarchy leading to the tools.
Question #3: How do I properly install these folders and tools from the "Additional Tools" dmg?
Installation of Command Line Tools for Xcode 10.2 beta
For the Command Line Tools, I double-clicked the downloaded command line tools dmg and got the "Command Line Tools (macOS Mojave version 10.14).pkg" file. I double-clicked the pkg file and the installation started. But when I got to the step where I click "Install" and enter my password, I get the message:
"The installation failed. The Installer could not install the software. The Installer could not install the software because there was no software found to install."
I downloaded the dmg a second time to make sure I had the complete file, but the result was the same. So, I decided to install the command line tools from the terminal. I ran:
sudo xcode-select --switch /Applications/Xcode-beta.app
followed by
xcode-select --install
The response was:
xcode-select: note: install requested for command line developer tools
And that was it. I then ran:
xcode-select --version
and the response was:
xcode-select version 2354
Question #4 (two parter): (1) Is 2354 indicating the version of command line tools and, if so, (2) is this the same version as the 10.2 beta version I downloaded?
I could not find anything from the Apple Developer download site as to what version number the 10.2 beta Command Line Tools is.
Question #5 (two parter): (1) Have I successfully installed the correct version of the Command Line Tools and, if not, (2) how do I properly install them?
Update #1: Just ran pkgutil --pkg-info=com.apple.pkg.CLTools_Executables and the response was:
package-id: com.apple.pkg.CLTools_Executables
version: 10.1.0.0.1.1539992718
volume: /
location: /
install-time: 1548388461
groups: com.apple.FindSystemFiles.pkg-group
I would think the version should be 10.2.something and that, therefore, xcode-select --install did not install the 10.2 beta version.
Update #2: Just downloaded "Command Line Tools (MacOS 10.14) for Xcode 10.1", double-clicked the pkg file and it installed fine. So, there appears to either be something wrong with 10.2 beta pkg file or some mismatch between it and my system, although as I mentioned, I'm doing this on a fresh install of macOS Mojave 10.14.3. Don't know if issue would still exist if I was using 10.14.2 or earlier.
Update #3: Experimenting, I eventually got an error message like:
... .pkg uses a deprecated pre-10.2 format (or uses a newer format but is invalid)
So I upgraded to macOS 10.14.4 beta (possible "newer format") to see if that would enable me to install the CLT, but same result. There does seem to be a set of command line tools that is installed by default with Xcode that resides in Xcode-beta.app/Contents and they can be selected in Xcode Preferences under "Locations", but they don't appear to be the same tools that would be installed by the downloadable .dmg from the Apple Developer site.
One thing I was able to do is drag the CLT .pkg file to the package utility Pacifist, then in the Content (not Resources) window, right click the top level pkg and select "Install". It does seem to install all of the CLT into /Library/Developer as would be expected. The down sides are, because installing via Pacifist bypasses the "Distribution" .exe file, no receipt is generated (although I don't know if receipts are generated for all .pkg installations or only when installing from the App Store), and no entry is made in the /var/log/install.log file. So, when you run
pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
you get:
No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.
I don't know what the side effects of this would be. If they are minimal or none, perhaps this is the only way to install the downloadable CLT at the moment. This also seems of value only if you have no previous installations of the CLT, because Pacifist isn't able to handle the removal packages that come as part of the installation for previous versions of the CLT.
Update #4: For the downloaded "Additional Tools" .dmg for Xcode 10.2 beta, since it has no installer, just folders, I copied every .app file in the folders to Xcode-beta.app/Contents/Applications and they are all now reachable and executable from the Xcode-beta Xcode > Open Developer Tool menu. The few things that weren't .app files (e.g Network Link Conditioner.prefPane), I copied to Xcode-beta.app/Contents into their original folder names (e.g. Xcode-beta.app/Contents/Hardware/Network Link Conditioner.prefPane). I don't know if this effects their usability or the ability of any of the apps that might need them to reach them, but without any additional guidance, it seemed like a reasonable thing to do for now.
So, on a spectrum that ranges from "This installation process is really lame" to "I'm really dumb", I'm not sure yet where this experience falls. But, beta or not, is the inclusion of basic installation instructions in the release notes asking for too much? (That's perhaps intended to be rhetorical as opposed to Question #6.)
Just an information: in the pkgutil output, at the end of the 'version' line, the long integer is the Unix timestamp for the creation date of the CLT's. For me:
$ pkgutil --pkg-info=com.apple.pkg.CLTools_Executables
package-id: com.apple.pkg.CLTools_Executables
version: 11.0.0.0.1.1567737322
volume: /
location: /
install-time: 1572589224
groups: com.apple.FindSystemFiles.pkg-group
$ date -r 1567737322 +"%d-%b-%Y %T"
06-Sep-2019 04:35:22
$
Switch Command Line Tools to Xcode beta
Once you have install your xcode-beta.
Install your commands line tools like usual, using the following code on your terminal
xcode-select --install
One you have installed commands line tools is the step to download the new ones
To do this, open your browser and look for apple developer resources download
Select view additional downloads, you will need to logIn in order to continue.
Once you have logIn, look for the file you are interested in, in my case was Additional Tools for Xcode 14 beta 5
Select download and wait.
Once is downloaded if you try to open it, you will see the following content on the folder.
It is time to open xcode
Look for xcode<preferences
Search for Locations.
And on command line tools select the ones you just downloaded
After I've installed Github Mac app on my macbook (running OSX Mavericks 10.9.2), I've tried to type git on the terminal, and a message appears and say:
xcode-select: note: no developer tools were found at '/Applications/Xcode.app', requesting install. Choose an option in the dialog to download the command line developer tools.
I've also already installed the "Command Line Tools" from Github Mac app preferences.
So, what is the problem?
Why I can not use the "git" terminal commands and Github Mac client app together?
I've search over the web for solutions, but anyone resolves my problem.
Try running xcode-select --install.
As far as I understand, the command line tools are compilers and other tools needed for development.
For background: prior to Xcode 5, you used to have to download Xcode and within Xcode's preferences choose 'Install Command Line Tools' (or use the command I listed above).
Edit: Corrects the install flag syntax
Installed the full XCODE (about 2 GB) in a brand new mavericks macbook, using App Store, then rebooted. Ran Xcode. Went to Preferences > Location, verified Command Line Tools shows up (v 5.0.2 5A3005).
In terminal, xcode-select -print-path shows /Applications/Xcode.app/Contents/Developer plus I can now run gcc --version and see version info.
So AFAIK command line tools are installed.
However, when I try to install homebrew, it opens the gui dialog offering to install XCode or the command line tools.
I don't want to end up double-installing, with conflicting paths, so any help on why the brew installer isn't "seeing" the commandline tools would be appreciated.
As noted in my comment, it is in fact a homebrew issue that it's not able to find the command line tools 'inside' Xcode due to Xcode recently changing where the command line tools were located... see these two issuesL github.com/Homebrew/homebrew/issues/24471 and github.com/Homebrew/homebrew/issues/20427
The solution was therefore to simply accept the option to install the command line tools when the gui window pops up after homebrew can't find them.
I tried to install the command line tools on Mavericks following the steps in this very useful post
> xcode-select --install
but after a few short seconds I get the message
This seems wrong. Does anyone know how to solve this problem?
Whenever I navigate to the page that #Nikos M. is suggesting
I get this message
I followed #Rich's suggestion and I was able to download the package and install it which I wasn't able to do before, but I've found that I still don't have access to a lot of the commands that I should like arp or diskutil just to name two that I've encountered recently.
Install them from here. You must be a registered developer.
Other solution is: in xcode click Xcode>Open Developer Tool>More Developer Tools
This should then take you to a link which will require a developer Apple ID sign in. From there, you'll be redirected after authenticating to https://developer.apple.com/download/more/ where you can manually download and install the Command Line Tools.
The tools are still free, but xcode-select --install is no longer supported.
To install the latest command-line developer tools from https://developer.apple.com,
Applications -> App Store -> Search -> XCode -> Install ... install
XCode if you don't have it.
Open XCode and close any pop-ups
Go to the Xcode menu > Open Developer Tool > More Developer Tools... this opens the correct website.
Find the newest version, download the dmg and install the package. The filename you're looking for is similar to "Command Line Tools (OS X 10.9).pkg"
I had this problem for months and finally found the solution.
The problem was: I had installed it before and removed it manually.
(I had problems with the bundled git. It was not the smartest move to do this.)
What i didn't remove were the files
/var/db/receipts/com.apple.pkg.CLTools_Executables.bom
/var/db/receipts/com.apple.pkg.CLTools_Executables.plist
Delete them, run xcode-select --install -> no error anymore
At least it worked for me. Hope it is helpful for somebody.
I get that "Your Session has Expired" message when I try to download from within the Chrome browser. If I navigate to the site with Safari and sign in with my developer credentials then the Command Line Tools dmg downloads without a problem. I do not have a paid developer account either, btw.
You can download your Command Line Tools from daw.apple.com, but try it from Safari instead of Chrome.
I tried it with Chrome for a few hours and apple would not recognize my id/password (it is the same as your AppleID). It required me to change my password after each third try, which was challenging because it would not let you use any password you've used in the last three years.
Signing in via Safari gave me no problems.
The file you are going to look for is Command Line Tools (OS X Mavericks) for Xcode - Late October
If your terminal still says you need to install command line tools, it may be an issue with gcc-4.2. I was able to confirm that was the issue by following my terminal message after I ran "bundle install" on my rails app. If this is your issue, you will do the following follow Housen's solution here. Best of luck
I spent the day trying to solve this problem. I believe the error messages are just confused about installing Xcode. The real problem I had was a need to update gcc compiler. This happened to me because I skipped Mountain Lion, where that occurred. This blog post was very helpful.
I solved it by open XCode UI, then adding my apple account
Xcode -> Preference -> Add my APPLE ID account
Then repeat the xcode-select --install
Try to install the command line tools following
Error Message "Xcode alone is not sufficient on Sierra"
brew seems checks if the command line tools installed in this path:
/Library/Developer/CommandLineTools
My case is: I tried to install brew on my new mac. After I installed Xcode, there was nothing in the above path but the command line tools were somehow installed to another location. (xcode-select -p tell me it was /Applications/Xcode.app/Contents/Developer)
The way in stackoverflow can install the command line tools to
/Library/Developer/CommandLineTools
Now I got brew working. But I am not sure if it is the best solution as there should be two copies of command line tools on my machine using this method.
I am running OSX Mavericks (10.9) and while trying to update a bundle in rails, I get the following error message:
"You have to install development tools first."
I have Xcode already installed and there seems to be no option to install the tools from within the Xcode 4.6. How can I download and install command line tools via terminal?
Incase, while trying to update a bundle, you get an error "You have to install development tools first." on OSX Mavericks (OSX 10.9), but you already have Xcode installed, you can still manually install the dev tools via terminal:
xcode-select --install
Do that and follow on-screen instructions. Your problem will be solved.
I summarized the steps in this blog entry "How to install command line tools on OSX Mavericks"
Installing command line tools in OSX 10.9 Mavericks changes slightly compared to previous versions of MAC OSX. Now you don’t need to install Xcode. You can install the Command Line Tools as stand alone.
Open Terminal
Type “xcode-select --install” in terminal (without quotes)
A pop-up windows will appears asking you about install tools
choose install tools
wait install to finish it will take 30 minutes
I summarized the steps in this blog entry "How to install command line tools on OSX Mavericks"
open terminal
and type
xcode-select --install
or open finder navigate to
/System/Library/CoreServices
and open Install Command Line Developer Tools.app