-
Notifications
You must be signed in to change notification settings - Fork 10
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
npm install fails on node-gyp rebuild with "gyp: No Xcode or CLT version detected!" #7
Comments
@prasanthmaran1 this library contains a native addon for extra performance in node environments, what this means is that you should have a c compiler installed on your system. This is fairly common in the node ecosystem. See instructions here: https://github.com/nodejs/node-gyp#on-macos In most cases this is as easy as running Let me know if that works. |
Thanks @schnerd package installed successfully... |
perfect work for me. using xcode-select --install on mac. Thank you. |
I had to re-install the xcode tools for some weird reason...
That is listed in the bottom of the guide (https://github.com/nodejs/node-gyp/blob/master/macOS_Catalina.md). So thank you! |
I do as this, too. |
I wouldn't ever trust a
|
following step help me to resolve this issue on Mac Catalina OS
|
This worked for me in MacOs catalina. |
Thank you !!! very much |
I hate that reinstalling the Xcode tools worked, but it did. I bought a brand new MBP today and installed Xcode on it for the first time a few hours ago (and xcode-select reported the tools were already installed). Really have no idea why this is necessary. Thanks, internet friends 🙏 |
It’s time for them to rename their X-code to XXX-code... |
If you don't want to re-install xcode, you can also point xcode-select to the existing installation:
Make sure to open xcode at least once after installation to accept the terms. |
I had a similar issue with a different package: node-gyp rebuild
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!
gyp ERR! configure error Running on $ xcode-select --install
xcode-select: error: command line tools are already installed,
use "Software Update" to install updates Fixed it by running the following: $ [sudo] xcode-select --reset |
I'm currently on Catalina, following the reinstall commands:
I use fish as a shell and it didn't like the $( ...) command. Just wanted to mention that to work around it quickly, I just went into the Vscode terminal window and in the shell dropdown choose 'select default shell', choose a new shell from the top list (I used bash), then hit the '+' to open a new bash console. Then I could follow the commands directly without wrecking my fish shell setup. |
In Fish just drop the dollar!
|
Please don't run Just run |
sudo rm -rf $(xcode-select -print-path) works for me |
thank you. thats solv my problem. |
Looks like |
This fixed it for me: |
I am having this error and nothing here has worked. |
Had the same issue.
I got the message
Even I used https://nektony.com/mac-app-cleaner to fully uninstall xcode and reinstalled xcode again from the app store. Hope it helps to solve your problem too |
Avoid using this command ever |
Reinstalled by 'xcode-select --install' but still facing the issue. |
@sumit0708 have you tried these above steps ☝️ |
Updating to macOS to latest version fixed this issue for me. macOS - 10.15.4 . Node - v12.16.1. npm - v6.13.4. |
Getting same, 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 '/'. |
I previously went through the steps to fix the issue via command line, but the exact same issue popped up again later. This time I installed via the Xcode interface, which takes you to https://developer.apple.com/download/more/?=for%20Xcode where you can download the latest tools under EDIT: It's happened again after updating Xcode. Looks like you just need to open Xcode, get prompted with "Install additional required components?", and click |
I tried uninstalling and reinstalling, that didn't work. The global node-gyp install made it work. |
This issue keeps coming up for me every so often; likely tied to minor upgrades to OS X. trash $(xcode-select -print-path)
xcode-select --install
# wait ten minutes... (◔_◔) Good luck all! |
This is the only thing that fixes it for me. |
My xcode recently updated and I ran into this problem for the second time. Instead of re-installing which I did the first time, I ran Worked perfect, thanks! |
not work |
Time and again, I have to install x-code what is the main issue?? |
Sometimes it works, sometimes it doesn't. |
@prasanthmaran1 hey mate, can you add this link: In similar fashion like @joe-nano did at the top of his initial post here: My issue background: On my machine |
Second time a row Catalina updates (10.15, 10.15.1) break CLT. Removing existing dir and re-installing CLT works, but it's pretty annoying. |
Save my life, thank you! |
https://github.com/nodejs/node-gyp/blob/master/macOS_Catalina.md. : this works for me. thanks |
Only thing that worked for me was a comment by inglkruiz on here: nodejs/node-gyp#1927 |
If you have a server response problem after Download the Command Line Tools for Xcode directly from https://developer.apple.com/download/more/ |
I've fixed this by forcing npm to use a later version of node-gyp (at least version 7).
This is hopefully a more permanent solution than always needing to re-install xcode-select tools. Unfortunately that is something I've found myself having to do time and time again. The only gotcha is that, in my case (using nvm to manage my node version), when I update node, I'll have to update this config again. Still, I'd rather that than reinstall xcode-select every time. Working good for me so far; YMMV. |
I have had an old node version after I have updated it to a new stable one it fixed my problem. |
This worked perfectly! |
error code
The text was updated successfully, but these errors were encountered: