Problems on Mavericks with only Command Line Tools installed

[OliverJAsh]

I have installed the Command Line Tools:

$ xcode-select --print-path
/Library/Developer/CommandLineTools

However, when anything tries to use node-gyp, I get the following error:

$ npm install bcrypt
npm http GET https://registry.npmjs.org/bcrypt
npm http 304 https://registry.npmjs.org/bcrypt
npm http GET https://registry.npmjs.org/bindings/1.0.0
npm http 304 https://registry.npmjs.org/bindings/1.0.0

> bcrypt@0.7.7 install /Users/Oliver/Development/sbscribe/node_modules/bcrypt
> node-gyp rebuild

xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

gyp: Error 1 running xcodebuild
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:424:16)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:789:12)
gyp ERR! System Darwin 13.0.0
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/Oliver/Development/sbscribe/node_modules/bcrypt
gyp ERR! node -v v0.10.21
gyp ERR! node-gyp -v v0.10.10
gyp ERR! not ok
npm ERR! weird error 1
npm ERR! not ok code 0

On Mountain Lion it was possible to use this without installing the whole of Xcode, rather just the Command Line Tools. Is it possible to do this on Mavericks? How can I get it working?

N.B. This is on a clean install of Mavericks.

[andessen]

+1

[kahwee]

+1

[w0rm]

I also have this problem, don't really want to install xcode.

[tonyyates]

+1

[freidamachoi]

+1

[wildjcrt]

+1

[btmills]

Had this same error installing contextify as pert of jsdom on a clean install of Mavericks. Unfortunately the workaround was to install Xcode.

[prestonparris]

Installing the latest version of command line tools for mavericks fixed the issue for me.

[gregdillon]

Hmmm...Still not working for me.

[shaneog]

👍 Latest Command Line Tools (late October) don't work for me either

[HyShai]

+1

[TooTallNate]

Everyone please try node-gyp v0.12.1 please. This is hopefully fixed.

[HyShai]

Still getting the error.

gyp ERR! node-gyp -v v0.12.1

[TooTallNate]

I'm getting reports that this is still an issue. Reopening.

However, it's an upstream gyp issues. Has anybody reported an issue on the gyp issue tracker that we can reference for here?

[victorhooi]

Hi,

I can confirm that I have this issue as well.

OSX 10.9 (Mavericks) with Command Line Tools for Mavericks (Late October) installed.

I've raised an issue with the Gyp project here:

https://code.google.com/p/gyp/issues/detail?id=383&thanks=383&ts=1385034279

Is that what you meant? I don't know much about the background to this issue - so if somebody (e.g. @TooTallNate ) could add proper details, that would be great.

Cheers,
Victor

[yixizhang]

＋1

[yixizhang]

Installing XCode as a whole fixed the problem for me.

[robrobbins]

+1 . Installing XCode but only because of this...

[Paxa]

suks :(

[breezewish]

I have installed the whole xcode but still get this error :( any ideas?

[akougblenou]

I am running on Mac OS X 10.7.5, I already had Xcode installed (v. 4.6.2) and just recently installed Command Line Tools but it is still not working. Any ideas?

[victorhooi]

Hi,

Is there any word on whether this will eventually work with just Command Line Tools, and not the full XCode suite?

It seems a bit weird to have to install 4-5 Gb worth of XCode, just to get this one thing to compile.

Cheers,
Victor

[Chicooz]

yes this sucks , i need a solution for this guys

[Chicooz]

i have xcode installed and i get the same issue

[dankohn]

Until this is fixed, the workaround to use node-gyp on Mavericks is:

1. Install XCode from the App Store
2. In terminal, enter sudo xcode-select /Applications//Xcode.app/Contents/Developer/

[giancarlo3g]

+1

[Pazzilivo]

+1

[TooTallNate]

Guys, I've reopened the ticket since this is apparently still an issue, but please stop +1'ing it here. There's really nothing I can do, it's up to the Google guys at this point: https://code.google.com/p/gyp/issues/detail?id=383

[jayhendren]

Zach, I’d like to know as well. I feel a little iffy about it myself. I honestly have no clue, because I’ve never built anything using the XCode development environment.

On Feb 9, 2014, at 6:08 PM, Zach Harkey notifications@github.com wrote:

I followed @Poohblah's recommendation and added a stub executable to my PATH and it fixed my immediate problems. But it feels pretty sketchy. Can anyone advise if this is gonna bite us in the ass later?

—
Reply to this email directly or view it on GitHub.

[ishanagr]

Thanks @Poohblah your suggestion fixed it for me 👍

[mtheoryx]

Any update on a better solution?

[jesstelford]

Whilst @Poohblah's solution works (and is the only solution that worked in this thread), I feel there has to be a better fix than this!

@TooTallNate - is this something you can fix again? I'm using node-gyp 1.0.1, and have made sure my npm version is using 1.0.1 too.

[whmountains]

Any better solution?

[cburmeister]

This still hasn't been fixed? I really, really do not want to install Xcode.

[jesstelford]

To re-iterate @Poohblah's solution:

The Error

xcode-select: error: tool 'xcodebuild' requires Xcode, but active developer directory '/Library/Developer/CommandLineTools' is a command line tools instance

The Solution

1. Run which xcodebuild in the terminal. If it gives no output, continue to step 2. If it gives output, then this solution will not work for you.

2. Create a file /usr/local/bin/xcodebuild. In that file, use your favourite editor to add the contents:

   #!/bin/bash
   
   exit 0

3. Save that file, and exit your editor.

4. Give the file the correct permissions by running sudo chmod a+x /usr/local/bin/xcodebuild

5. You're done! Re-run he command that caused the error.

[neverfox]

I get this warning (whether I use 0.10, 0.11, 0.12, or io.js) but then everything seems to work fine anyway. I do get output from which xcodebuild (/usr/bin/xcodebuild) FWIW. I would prefer not to get the warning though, obviously, as it makes one wonder if everything is really alright.

[ilei]

Can you give me an answer?

[jesstelford]

@ilei 42.

[Ajithsou]

I have faced the same problem and resolved by installing the xcode6.

[HipsterZipster]

Problem still exists in Yosemite. Wish there was a way NOT to install 3GB xcode 👎

[prashcr]

Not 3GB. Fully installed Xcode is 6GB according to AppCleaner, probably including libraries and frameworks outside Xcode. Utterly ridiculous that I have to give up 6GB on my 100GB SSD for something I'll never use.

[itajaja]

thanks @jesstelford, your solution worked perfectly! 👍

[u2]

Thanks @Poohblah, it works for me.

[bdwyertech]

You can also symlink /usr/local/bin/xcodebuild to /usr/bin/true

# Fix XcodeBuild Issue
if [[ -d '/Applications/XCode.app' ]] || [[ -d '/Developer/Applications/XCode.app' ]]; then
  echo 'Xcode Seems to be installed...'
else
  if [[ ! $(xcodebuild | grep 'requires Xcode') ]]; then
    echo 'Fixing the Xcodebuild issue by symlinking xcodebuild to true'
    ln -s /usr/bin/true /usr/local/bin/xcodebuild
    source '/etc/profile'
  fi
fi

[cebor]

Also getting this error ...

[mourner]

ln -s /usr/bin/true /usr/local/bin/xcodebuild hint by @bdwyertech works perfectly, although I'm still not sure whether it has any unwanted side effects.

[jelpern]

I'm also getting this error. @bdwyertech @mourner can you explain where to put this code and how to run it, for someone who is less familiar with bash scripts?

Has anyone confirmed whether this works on El Capitan?

The only silver lining I've seen is that Xcode seems to have dropped in size down to only 4GB ...

[MarcDiethelm]

@jelpern: @bdwyertech's script (thank you!!) works for me under El Capitan (OSX 10.11). You can just put it in a new file anywhere, and call it e.g. fix-xcodeless-build.sh. Make it executable chmod +x fix-xcodeless-build.sh. And run it: sudo ./fix-xcodeless-build.sh.

[jelpern]

Thank you @MarcDiethelm. Would there be any downside to putting this in my .bash_profile? Also why does this need to be run as sudo?

[tcelestino]

Thanks @jesstelford, your solution worked for me on El Capitan.