-
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
gyp ERR! stack Error: make
failed with exit code: 2
#1694
Comments
Yes, that error describes the problem. [email protected] seems very old (https://github.com/apiaryio/protagonist/releases) and is setting I'd suggest updating to a later version of protagonist to see if the problem has been fixed, and if it hasn't raise an issue on their tracker: https://github.com/apiaryio/protagonist/issues |
Looks like you need at least [email protected]: https://github.com/apiaryio/protagonist/pull/158/files |
@richardlau You are absolutely right! Thank you very much for your time you took to reply and sorry. |
In case someone else finds their way here for the same reason as I did: In my case it wasn't "protagonist" (it was "fsevents" and something else). My fix was to downgrade node from 12 to 11; I was in a project created on Node 11 and then I tried running it on a new computer with Node 12. Ideally I'd "roll forward" and update dependencies until it works on Node 12, of course, but I didn't want to do that now. |
Follow these steps to resolve the issue. 1: Make sure you have build-tools installed. Source: https://codeforgeek.com/make-failed-with-exit-code-2/ |
For those who are using AMI 2, I resolve it using sudo yum groupinstall "Development Tools" Since my errors were
|
I also experienced this issue, and it seemed my error also referenced fsevents. I believe this was also due to upgrading to Node 12. However @henrik I was able to resolve the issue without downgrading by following @codeforgeek's instructions for the most part.
|
if using yarn:
|
@jorwan thank you! That worked seamlessly solving the issues for me. |
yarn upgrade worked for me! i was using node 12 on mac 10.15 |
worked for me in MacOs Catalina |
I had the exact same issue after updating to Macos Catalina. After hours wasted looking for a solution, I fixed it by downgrading Node.js to 10.17.0. I hope this helps :) |
I downgraded to 10.16.0, and now its working. |
Just want to know why node-gyp not support node version 12 or latest.? |
It does (assuming you are using an up to date version of node-gyp). Issues like these where downgrading Node.js "fixes" the issue are because the module being installed or one of its dependencies is not compatible with the later Node.js version. |
Downgraded to v10.18.0 via brew install node@10, It's now working. |
In my-case it was failing on Linux-mint 19.2, for some reasons on run-time gcc++ was not accessible. build-essential package is a reference for all the packages needed to compile a Debian packages. It generally includes the GCC/g++ compilers and libraries and some other utilities. Informational for list of build-essential packages can be found on build-essentials |
This is really frustrating. I strongly hope node-gyp can work with node 13. |
I look-read-apply many gyp error solution, and only worked "in my case" React Native Environment Info: |
Node 11 is no longer supported, please choose an LTS version instead - 10 or 12. Compile errors like this are almost certainly a problem with the addon you're compiling, it's not something we can change here. You need to take it up with the addon author - they need to upgrade their code to work with a newer Node.js, or you need to upgrade the version of the addon you're installing because there's a good chance they've already released a new version. |
I downgraded to Node 10.x with Mac OS Catalina, and the issues were solved. I originally had 14.x and tried 12.x too, with no luck. |
work ! |
yarn global upgrade
cd ${yourReposDir}
rm package-lock.json
npm install |
It works with windows WSL! |
On non macOS platforms, the fsevents messages are warnings, not errors. |
try |
For Mac users |
;-) it is copied from https://github.com/nodejs/node-gyp/blob/master/macOS_Catalina.md |
aaah thx |
|
Got the same error, If you have installed node or yarn with brew, uninstall node and reinstall it, |
Can confirm @kozr after downgrading node to 10 it works. |
Had to downgrade to node version 14 due to this error 😩 |
I am trying to npm install my packages, and it seems a package named
protagonist
needsnode-gyp
I have literally tried everything I found online (issues here included) and still cant solve this.
2 days I have spent searching around, changing node versions, reinstalling
python
andxcode tools
etc, its driving me crazy.Where should I focus? Could this be the problem? :
clang: error: invalid deployment target for -stdlib=libc++ (requires OS X 10.7 or later)
But I have OS X 10.14...I am literally at my wits end.
Any help really appreciated
Node Version:
$ node -v
v8.11.1
(tried with a lot of other versions too: 6.X, 10.X, etc)
Platform:
macOS Mojave 10.14.3
Darwin USERNAME_Macbook-Pro.local 18.2.0 Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~1/RELEASE_X86_64 x86_64
Compiler:
Module:
form the error log, its
[email protected]
Python Version (if it matters):
$ python -V
Python 2.7.16
Xcode verion (if it matters):
$ /usr/bin/xcodebuild -version
Xcode 10.1
Build version 10B61
Verbose output (from npm or node-gyp):
The text was updated successfully, but these errors were encountered: