9/17/2023 0 Comments Xcode select install not working![]() ![]() Ive run cd /opt/homebrew git fetch git reset -hard origin/master (my homebrews dir is /opt/homebrew). I just want my iMac to act like my MacBook :( I rather not have to manually set my command line toolchain everytime I update to a new Xcode. The reason was the installed Homebrews version was too old. ![]() Xcode-select: error: command line tools are already installed, use "Software Update" to install updates ), to point to an alternate toolchain.Īgain, how to reset my iMac toolchain state to the default behavior so that my command line toolchain is at /Library/Developer/CommandLineTools and updated to 5.2 (from inside my Xcode.app)? These tools are included in the new free developer membership. (or set that inside Xcode Prefs, Location. To get the new SDK and Xcode beta files, go to /download/ and log in with your Apple ID. If you dont want to install nor use Xcode (I dont) you can install only command tools for Xcode (please see Edit) Preconditions: you have AppleID Solution. I want the system default at /Library/Developer/CommandLineTools updated to the latest 5.2, not use xcode-select -s. So i try: xcode-select -install In forums/google they say it will start the installation eg. Try on the command line, run xcode-select -p, the result points to you copy of Xcode.app, not /Library/Developer/CommandLineTools. i try to install/update Xcode5 on OS X 10.9.1. So this "fix" in Xcode Preference Locations, Command Line Tools, and choosing Xcode 14 (11E146) is just doing the same as xcode-select -s. The result is exactly the same as I manually run " xcode-select -s ~/Applications/Xcode.app": the command line toolchain is just pointing to my Xcode location. ![]() Re-open Xcode, open Xcode Preferences Locations, Command Line Tools, it's now empty, then I choose "Xcode 14 (11E146)", Xcode then ask admin password to install, just like it did when I first install new version and run it. However it did give me a list of valid options where I saw the reset option. I tried running Sudo xcode-select -update but that wasnt a valid command. xcode-select: error: command line tools are already installed use 'Software Update' to install updates. ![]() xcode-select: error: command line tools are already installed, use 'Software Update' to install updates. Doing this errored out because It was already installed. According to Xcode-select, see output below CLT is already installed: sbezverksbezverk-mac-2 sudo xcode-select -install. So I quit Xcode, went on the command line, run xcode-select -r to reset back to system default. After upgrade to Big Sur git stopped working and it keeps prompting to install CLT. Since I already ran " xcode-select -s ~/Applications/Xcode.app", when I went to look at Xcode Preferences Locations, Command Line Tools, it's already pointing at " Xcode 14 (11E146)". If command line tools are not installed run: xcode-select -install. As long as everything worked, I'd clone that to my main drive or repeat the wipe/reinstall process - whichever is easier for you to perform."fixed" it by going into Preferences for Xcode, Locations, Command Line Tools, and choosing Xcode 14 (11E146) To check if command line tools are installed run: xcode-select -version // if installed you will see the below with the version found in your system // xcode-select version 1234. In your terminal app, run xcode-select to see the set of options. I'd make a junk admin user that I'll delete and use that user to install Xcode and the command line tools and then finally restore from Time Machine. You can see what Xcode set of command-line tools youre using with the xcode-select command. If this happened to me, I'd simply change my Time Machine to exclude system files and then install a new OS onto a spare volume. This URL is fairly open (even the search engines can index it) but you might need to make a free Safari or free Mac developer account to log in and get this package. Rather than mess with that, why not just download the stand alone installer and wait for a new version of Xcode to clean up your receipts database for you? The command line tools are installed like other OS X packages, so you may need to delete the receipt file from the receipts database (which used to be trivial since you could delete the file from /Library/Receipts but now is more complicated and needs a short article on the receipts database). You need to have the Xcode Command Line Utilities installed (and updated): run xcode-select -install in the terminal. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |