-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this an Issue with MACOS catalina? #1927
Comments
Did you add that "I'M RUNNING XCODE 11.2beta" to the output? That may be the main problem, using a beta version of xcode. But you could also try installing the command-line tools to solve this: |
No I didn’t I was merely saying that I do have XCode installed |
I have the same issue |
please try installing the commandline tools like I suggested, it's different to the full xcode |
When I run xcodebuild i get this
|
When I run gcc -v I get this
|
See #569. |
Thanks that works. I will let my users know. |
@joe-nano Can this issue be closed? |
Same issue to me. node-gyp rebuild fails. I'm using 10.15 Catalina and installed XCode CLI by Related source: node-gyp/gyp/pylib/gyp/xcode_emulation.py Lines 1298 to 1318 in a84b885
Is there a way to fix it without installing full XCode.app? |
|
Returns:
|
Same issue. |
Could I please get a few of you to run
If you get nothing returned, please do |
It returns nothing Last login: Sun Oct 20 15:22:02 on ttys002
mkellsy@mikes-laptop ~ % /usr/sbin/pkgutil --packages | grep CLTools
mkellsy@mikes-laptop ~ % Heres the same thing with grep Xcode mkellsy@mikes-laptop ~ % /usr/sbin/pkgutil --packages | grep Xcode
com.apple.pkg.XcodeSystemResources
com.apple.pkg.Xcode When you try to install CLT mkellsy@mikes-laptop ~ % xcode-select --install
xcode-select: error: command line tools are already installed, use "Software Update" to install updates
mkellsy@mikes-laptop ~ % |
This worked for me.
This uses the full Xcode CLT and node-gyp works. |
OK. Thanks. The goal is NOT to install full Xcode. Perhaps we needed to |
Uninstalling command-line tools as described in the official documentation, then run |
Yep, only Xcode. For my Mac users, I am directing them to install full Xcode. Our team finds the instructions much easier then this https://developer.apple.com/library/archive/technotes/tn2339/_index.html. Note that many of our users will not go to the Apple developer site. However they can tolerate a command here and there. |
On Catalina with command line tools (but no Xcode) I'm getting the same as others:
Naïve question: Is there a reason the script needs to know the version? Is it not enough to just check |
The comment says this check was ported from Homebrew: node-gyp/gyp/pylib/gyp/xcode_emulation.py Line 1298 in a84b885
FWIW, in macOS 10.14 and greater Homebrew checks whether CLT need to be installed based on the presence of git: |
@nodejs/build This issue is difficult to debug at scale because Travis CI does not yet support Catalina macOS 10.15 https://docs.travis-ci.com/user/reference/osx/#macos-version Is there another way to test these cases on Jenkins? |
I think we'd need someone to set up a Catalina host at MacStadium. I think our most active MacStadium deployer might have been @gdams but I'm not sure they're active on the project anymore. Unless gdams jumps in here with a "Yeah, let me get that set up for you", more definitive word on whether this can happen easily/quickly will have to come from @rvagg or @mhdawson, I think. I'm guessing it's not easy or quick since we're always several versions behind on our macOS hosts in Jenkins. But again, I'm speculating. |
Sadly no, so far we haven't even been able to get High Sierra on MacStadium. Image availability and other complications. We do have some new Mac infrastructure we're introducing (and managing ourselves unfortunately) but that's a work in progress. Everything about this is hard. Also, I'll be holding back my laptop from Catalina, I can't afford the chaos, so I can't even help figure this all out. |
I edited the original post with the fix that @gibfahn added to #569. |
@joe-nano, et al, Can we close this issue? |
I did the manual download and I still can't get it working, and our pipelines are failing now too presumably because the build machines are using Catalina too |
@suzck There were a couple cases where it was recommended you reset the xcode-select path. Which version of xcode CLI |
Same here. |
I just had the same issue which is getting quite repetitive every time I update macOS. This worked for me:
|
I'm just metoo'ing on this issue as requested in the macOS_Catalina.md. Did all the steps, including manually deleting the developer tool directories and downloading the .dmg from Apple web site for XCode 12 command-line tools. Acid test runs correctly yet I get the build error. Unfortunately I'm trying to work with a large open source project that hasn't apparently adopted node-gyp v7 yet so I'm stuck here. |
@tonimelismasalesforce does the solution proposed in #2235 work? |
I'd like confirmation from someone that #2235 (adding an |
Downloading it directly from https://developer.apple.com/download/more/ worked for me: Command Line Tools for Xcode 12.2 beta 3 |
Uninstalling and reinstalling works, but I have to do this quite often and xCode is pretty large and takes ages to reinstall, there must be a better way than having to reinstall it every few days |
Yes. #2235 |
This is what worked for me: downloading the non-beta Command Line Tools for Xcode 12, deleting the existing directories, installing it and then running: sudo xcode-select --switch /Library/Developer/CommandLineTools Part of the confusion is that every version seems to use a different path. The non-beta path is as above, while the more recent ones are under either names=("/Library/Developer/CommandLineTools" "/Applications/Xcode-beta.app/Contents/Developer" "/Applications/Xcode.app/Contents/Developer")
for name in ${names[*]}; do
if [[ -d $name ]]
then
echo Selecting $name
sudo xcode-select --switch $name
fi
done |
#2244 which just landed works for me. |
This worked for me. |
worked for me too |
Started getting "No receipt for 'com.apple.pkg.CLTools_Executables' found at '/' -npm" after opening Terminal following the Catalina 10.15.7 supplemental update - this solution fixed it great. |
Just wanted to comment that following the instructions for "I did all that" (https://github.com/nodejs/node-gyp/blob/master/macOS_Catalina.md#i-did-all-that-and-the-acid-test-still-does-not-pass--) resulted in a broken XCode installation. The XCode.app file has been removed, but the App Store thinks it's still installed, so doesn't present an option to re-install. To re-install, I had to manually delete the Xcode.app file from /Applications. |
This works for me after installing the Command Line Tools for Xcode from apple(https://developer.apple.com/downloads/index.action). I have this issue every time the command line tools was updated by Mac's system software update. |
Should this check still be in place for folks on Big Sur? It seems that every so often when there's an update from Mac this comes back. |
get sign |
i had this error when running it as a dependancy. once i installed it globally $ npm i -g node-gyp it worked fine. hope this helps someone who doesnt want to re-download xcode. |
I had this error and tried everything except installing the whole XCode 7Go package.
|
the acid test (https://github.com/nodejs/node-gyp/blob/main/macOS_Catalina.md#the-acid-test) fails every time because https://github.com/nodejs/node-gyp/raw/master/macOS_Catalina_acid_test.sh does not exist (404). The command should be: |
EDITED FOR PEOPLE JUST GETTING HERE:
node-gyp v7 should solve these issues.
Please follow the steps in macOS_Catalina.md
No receipt for 'com.apple.pkg.CLTools_Executables' found at '/'.
No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.
No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.
gyp: No Xcode or CLT version detected! I'M RUNNING XCODE 11.2beta
gyp ERR! configure error
gyp ERR! stack Error:
gyp
failed with exit code: 1gyp ERR! stack at ChildProcess.onCpExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:351:16)
gyp ERR! stack at ChildProcess.emit (events.js:198:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Darwin 19.0.0
gyp ERR! command "/usr/local/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Users/drjosephdavids/node_modules/keccakjs/node_modules/sha3
gyp ERR! node -v v10.16.3
gyp ERR! node-gyp -v v5.0.5
gyp ERR! not ok
npm WARN enoent ENOENT: no such file or directory, open '/Users/drjosephdavids/package.json'
npm WARN drjosephdavids No description
npm WARN drjosephdavids No repository field.
npm WARN drjosephdavids No README data
npm WARN drjosephdavids No license field.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] install:
node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/drjosephdavids/.npm/_logs/2019-10-16T17_41_20_021Z-debug.log
Verbose output (from npm or node-gyp):
The text was updated successfully, but these errors were encountered: