Xcode is not currently available from the Software Update server

XcodeMacosMacportsOsx Mavericks

Xcode Problem Overview


I have problems with my macport after update to OS X 10.9.

I try to follow this manual https://trac.macports.org/wiki/Migration to fix them.

But when I install Command Line Tools:

> xcode-select --install

I get message

> Can't install the software because it is not currently available from > the Software Update server.

Meanwhile I successfully updated my other machine to OS X 10.9. and installed command-line tools with no problems, so they must be available.

What is the problem here?

Xcode Solutions


Solution 1 - Xcode

You can download the command line tools for OS X Mavericks manually from here:

Solution 2 - Xcode

For OSX 10.11 or more you can download from here https://developer.apple.com/download/more/.

(The link in the accepted answer doesn't display command line tools for El Capitan (OSX 10.11))

Solution 3 - Xcode

If you are trying this on a latest Mac OS X Mavericks, command line tools come with the Xcode 5.x

So make sure you have installed & updated Xcode to latest

after which make sure Xcode command line tools is pointed correctly using this command

xcode-select -p

Which might show some path like

> /Applications/Xcode.app/Contents/Developer

Change the path to correct path using the switch command:

sudo xcode-select --switch /Library/Developer/CommandLineTools/

this should help you set it to correct path, after which you can use the same above command -p to check if it is set correctly

Solution 4 - Xcode

I faced same problem of Can't install the software because it is currently not available from the Software Update Server. You may try following steps instead to make the Software Update initiate update for the Command Line Tools.

  1. Check if Command Line Tools Update is mentioned in your list of softwares to be updated by using following command: softwareupdate -l
  2. If Command Line Tools Update is not mentioned in that list, then manually make it part of the list using following command which will create a temporary file: sudo touch /tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress
  3. Verify that the list now has the Command Line Tools mentioned by running softwareupdate -l again.
  4. Now, press Cmd+Space to initiate Mac's Spotlight Search. Search for Software Update. Start the Software Update.
  5. That will show you following kind of dialog for installing the Command Line Tools. Install away the update and be merry. :) enter image description here
  6. Remove the temporary file created in Step 2: sudo rm /tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress.

Solution 5 - Xcode

I deleted the command tools directory given by xcode-select -p due to npm gyp error.

xcode-select failed to install the files with the not available error.

I ran the Xcode application and the command tools installed as part of the startup.

npm worked.

However this didn't fully fix the tools. I had to use xcode-select to switch the path to the Developer directory within the Xcode application directory.

sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer  

MacOS catalina.

Solution 6 - Xcode

I just got the same error after I upgraded to 10.14 Mojave and had to reinstall command line tools (I don't use the full Xcode IDE and wanted command line tools a la carte).

My xcode-select -p path was right, per Basav's answer, so that wasn't the issue.

I also ran sudo softwareupdate --clear-catalog per Lambda W's answer and that reset to Apple Production, but did not make a difference.

What worked was User 92's answer to visit https://developer.apple.com/download/more/.

From there I was able to download a .dmg file that had a GUI installer wizard for command line tools :)

I installed that, then I restarted terminal and everything was back to normal.

Solution 7 - Xcode

I know this is an old post but I also ran into this problem today. I found out that when I executed sudo softwareupdate -l the Command Line Tools were listed as an update, so I installed them using sudo softwareupdate -i -a.

Solution 8 - Xcode

This error can occur if you are using a software update server which doesn't host the required package.

You can check this by running

defaults read /Library/Preferences/com.apple.SoftwareUpdate

and seeing if you have an entry called CatalogURL or AppleCatalogURL

You can point back at the Apple software update server by either removing this entry or using the command

sudo softwareupdate --clear-catalog

And then run the command line tools install again.

Solution 9 - Xcode

I got the same issue on MacOS Catalina.

I think I identified the root cause: I have switched the default Apple ID account and the new one was not activated as a Developer account. When I ran the xcode-select --install command, I got the same error as stated in the issue description.

After reading this post on stackoverflow, I went on https://developer.apple.com/downloads and I was asked to accept Developers terms. I think it enabled my account as a developer one. Then, I tried to run xcode-select --install again and it worked.

Solution 10 - Xcode

The command

> xcode-select --install

proposes 3 options: Get Xcode; Not Now; Install.

When I choose to get full Xcode the command finished successfully. It took a while, but this way I was able to complete all macports migration instructions.

Solution 11 - Xcode

Once you get the command line tools loaded as described by Nikos M in his excellent answer above you will need to agree to the gcc license and if you are using ruby gems you may need to link llvm-gcc as gcc-4.2.

If you do not do these the gem install will report "You have to install development tools first." after you have already installed them.

The steps are:

sudo gcc
sudo ln -s /usr/bin/llvm-gcc /usr/bin/gcc-4.2

The gcc must be run once under sudo so Apple can update their license info, you don't need an input file, it will update the license before it checks its arguments. The link is needed so that ruby 1.9 can find the compiler when building certain gems, such as the debugger. This may be fixed in ruby 2.x, but I'll cross that bridge when I get there.

Solution 12 - Xcode

I had to run Xcode.app and agree to the License Agreement

Setup: Brand new MacBook with Mavericks, then brew install and other c/l type things 'just work'.

Solution 13 - Xcode

I solved this by going to the App Store and installing Xcode.

It was a pretty large 11GB install, so this is probably overkill. But, as a last resort, it seems to have solve my issues. In the middle of the installation (well around 10GB), Mac OS told me there was an update to Command Line Tools for Xcode. Performing this installation won't fix anything until Xcode is fully installed.

Once the install is done, it should start working (after you accept the license agreement).

Solution 14 - Xcode

Command + Space

Search for Xcode

Open it and accept license

Then run again from terminal xcode-select --install

Solution 15 - Xcode

Had the same issue and was getting the same error. When i ran xcode-select -p, it gave output as /Library/Developer/CommandLineTools. So that means xcode was already installed in my system. Then i ran steps as given on this answer. After which any command which required xcode ran successfully.

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
Questionklm123View Question on Stackoverflow
Solution 1 - XcodeNikos M.View Answer on Stackoverflow
Solution 2 - Xcodeuser92View Answer on Stackoverflow
Solution 3 - XcodeBasavView Answer on Stackoverflow
Solution 4 - XcodeUsmanView Answer on Stackoverflow
Solution 5 - XcodeInterlatedView Answer on Stackoverflow
Solution 6 - XcodeStephen MarshView Answer on Stackoverflow
Solution 7 - XcodeRoyView Answer on Stackoverflow
Solution 8 - XcodeLambda WView Answer on Stackoverflow
Solution 9 - XcodevdsbenoitView Answer on Stackoverflow
Solution 10 - Xcodeklm123View Answer on Stackoverflow
Solution 11 - XcodePeter WoosterView Answer on Stackoverflow
Solution 12 - Xcodezack999View Answer on Stackoverflow
Solution 13 - XcodeShortFuseView Answer on Stackoverflow
Solution 14 - XcodeSukeerthi AdigaView Answer on Stackoverflow
Solution 15 - Xcoderajya vardhanView Answer on Stackoverflow