GYP ERR! build error. stack Error: 'make' failed with exit code 2

Question

I am currently working on a nodejs web application I am having trouble pushing the application online with cloud foundry. I did some research on the errors and it seems that maybe some of the packages being installed have some conflicts.

This is the package.json file.

{
  "dependencies": {
    "c3": "^0.4.12",
    "cfenv": "1.0.0",
    "cloudant": "^1.8.0",
    "dygraphs": "^2.0.0",
    "express": "4.5.1",
    "getmac": "1.0.6",
    "http": "0.0.0",
    "mqtt": "1.0.5",
    "properties": "1.2.1",
    "save": "^2.3.0",
    "sockjs": "0.3.9",
    "websocket-multiplex": "0.1.x"
  },
  "description": "description.",
  "license": "UNLICENSED",
  "main": "app.js",
  "repository": {
    "type": "git",
    "url": "<gitUrl>"
  }
}

This is the error I encounter when I try to push the application via cloud foundry. This similar error happens when I npm install after deleting all the content of the node_modules folder.

../src/bufferutil.cc:32:50: error: call of overloaded 'NODE_SET_METHOD(v8::Local<v8::FunctionTemplate>&, const char [6], void (&)(const v8::FunctionCallbackInfo<v8::Value>&))' is ambiguous
     NODE_SET_METHOD(t, "merge", BufferUtil::Merge);

../src/bufferutil.cc:32:50: note: candidates are:
In file included from ../src/bufferutil.cc:8:0:
/root/.node-gyp/8.0.0/include/node/node.h:257:13: note: void node::NODE_SET_METHOD(v8::Local<v8::Template>, const char*, v8::FunctionCallback)
 inline void NODE_SET_METHOD(v8::Local<v8::Template> recv,
             ^
/root/.node-gyp/8.0.0/include/node/node.h:270:13: note: void node::NODE_SET_METHOD(v8::Local<v8::Object>, const char*, v8::FunctionCallback)
 inline void NODE_SET_METHOD(v8::Local<v8::Object> recv,
             ^
bufferutil.target.mk:95: recipe for target 'Release/obj.target/bufferutil/src/bufferutil.o' failed
make: *** [Release/obj.target/bufferutil/src/bufferutil.o] Error 1
make: Leaving directory '/home/WibiSmart-Bluemix-App/node_modules/bufferutil/build'

gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:285:23)
gyp ERR! stack     at emitTwo (events.js:125:13)
gyp ERR! stack     at ChildProcess.emit (events.js:213:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:197:12)
gyp ERR! System Linux 4.4.30-ti-r64
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 /home/WibiSmart-Bluemix-App/node_modules/bufferutil
gyp ERR! node -v v8.0.0
gyp ERR! node-gyp -v v3.6.1
gyp ERR! not ok

Did anyone else encounter this issue, or knows how to fix it?

Whenever you encounter such errors, the *actual* error(s) will appear *before* these lines you've currently posted *in the console*. — mscdex, Jun 01 '17 at 20:50
@mscdex I added the lines of code I am getting before the error — Michael Vaquier, Jun 02 '17 at 12:26
@opiethehokie What would be the command to do so? It seems to me that the **bufferutil** comes up a lot, would anyone know what that is? — Michael Vaquier, Jun 02 '17 at 13:47
For Mac OS Catalina, downgrading to Node 10.x solved my problem. — kolistivra, May 05 '20 at 14:09

noone · Answer 1 · 2020-03-12T05:26:54.430

158

It worked after deleting package-lock.json and re run npm install

If you are using yarn to build your program delete yarn.lock and re run yarn install

edited Mar 12 '20 at 05:26

answered Apr 09 '19 at 10:07

noone

6,168
2
42
51

162

I hate it when this is the solution – Paul Razvan Berg Sep 28 '19 at 21:26
2

This worked for. In my case it was `yarn.lock` file which I had to delete. – Rishi Vedpathak Nov 18 '19 at 05:49
yes.. if you use yarn to build instead of npm. I'll update my answer.. thank you – noone Nov 18 '19 at 08:13
npm upgrade should update all packages to latest. See https://docs.npmjs.com/cli/v7/commands/npm-update or https://www.npmjs.com/package/npm-upgrade – John Jun 25 '21 at 08:45
6

@PaulRazvanBerg I hate it much more when this ISN'T the solution. – Andor Németh May 20 '22 at 07:05
1

Holy crap, can't believe it was as simple as that!! – faniva Jul 04 '22 at 14:12
What this is most likely doing is the same thing as a npm upgrade, I think. You could try upgrading bcrypt, if you depend on it directly. – jpaddison3 Sep 29 '22 at 14:35
Do me a big fever – bobo pei Jun 05 '23 at 13:17

piscator · Answer 2 · 2022-12-19T08:45:25.703

44

In our case (since make failed), this issue could be resolved by installing the build / development tools:

Ubuntu / Debian:

apt-get install -y build-essential

CentOS:

yum install gcc gcc-c++ make

Fedora 23 and above:

dnf install @development-tools

macOS:

xcode-select --install

If this is not the solution, you might want to try to upgrade or downgrade node, remove package-lock.json and the node_modules folder, and then re-run npm install.

edited Dec 19 '22 at 08:45

answered Jan 13 '20 at 15:36

piscator

8,028
5
23
32

3

How to do this for mac? – John Jun 25 '21 at 08:45
For now I'm trying this..not a huge fan of homebrew or ruby, but if it works.... https://docs.macstadium.com/docs/install-osx-build-tools – John Jun 25 '21 at 08:49
Xcode is installed. I am running on MacOS 11.4 - I'm wondering if I'll be forced to update the system before I can move forward with this issue. Unfortunately my internet is garbage and it's an 8GB download - which always fails a GB or 2 into the download, and then wants to start over again from the beginning. Any idea if this is critical to making it work? – John Jul 05 '21 at 21:41
@John I don't expect you need to update macOS. Did you also install the Command Line Tools for Xcode? – piscator Jul 06 '21 at 06:53
That's it. After two days I stumbled here. Solved for Ubuntu 22.04.1 (same solutions in 3 different machines) – Marcelo Scofano Diniz Dec 18 '22 at 19:44
fixed my problem on ubuntu 22.04 – Pouya Samie Jun 14 '23 at 09:41

score 24 · Answer 3 · answered May 07 '19 at 07:38

24

This has been old yet consistent issue well documented at: https://github.com/nodejs/node-gyp/issues/809

For me the error mentioned the version numbers like:

gyp ERR! System Darwin 17.7.0
gyp ERR! node -v v12.1.0
gyp ERR! node-gyp -v v3.8.0

After attempting all the possible combinations of solutions (modify ~/.npmrc, remove ~/.node-gyp, clear the npm cache, delete node_modules and even restart the system), what worked with me was downgrading the node.

I believe the versions mentioned in the log for node and node-gyp are incompatible. So I reverted to an older node version which worked like a charm.

npm install -g node@11.10.0

There should be a clear documentation describing breaking changes and compatibility issues between the two.

answered May 07 '19 at 07:38

Slartibartfast

1,592
4
22
33

3

This is the answer I've been looking for for 3 days!! Although I was experiencing the problem inside a Docker container (rather than on a host machine), it does sound like I've been down the same route as you - trying to re-install node, clearing caches etc. For me, basing the container on `node:current-alpine` was the mistake (version 16 at time of writing). Changing to `node:12.2.0-alpine` fixed my problem and allowed `npm install` complete. I suspect that the underlying reason for my resolution is the same as yours -- the older Docker container essentially downgrades the version of node. – cartbeforehorse Jun 16 '21 at 23:34
1

How can one check if a specific version of `node-gyp` is a compatible with a specific version of `node`? – Paul Razvan Berg Jul 14 '21 at 12:33
1

This works for me. Additional resources to the answer: (1) https://stackoverflow.com/questions/47008159/how-to-downgrade-node-version#answer-50287454 (2) https://nodejs.org/en/download/releases/ – Blues Clues Jul 25 '21 at 18:23
2

For me I down graded to version 14 from version 16 of node and the issue went away. – mashgreat Jul 01 '22 at 08:29

score 23 · Accepted Answer · answered Jun 02 '17 at 15:38

23

Figured out the issue. Some of the npm packages were not up to date. I modified the package.json to install all the latest versions of all packages and the error was fixed.

answered Jun 02 '17 at 15:38

Michael Vaquier

1,621
2
10
19

9

how to do that ? – yas17 Jan 15 '20 at 12:48
4

yes, how to check peer dependencies of libraries and update safely ? – Anand S Feb 26 '20 at 05:10
you may try yarn-check package it is very helpful – 0xFK May 14 '20 at 02:34
What if that is not an option? – Anshuman Kumar Mar 21 '23 at 14:40
Then that is not an option. – OutOfThisPlanet Jun 18 '23 at 21:38

score 15 · Answer 5 · answered Sep 07 '18 at 18:46

15

For other people that stumble into this exact problem:

In my case, the server node version was set to an older version in my package.json file than what my local environment was running. So check what you are running locally with:

node --version
-> 8.11.3

Then look at your server setting in your package.json:

{
  "name": "myapp",
  "version": "0.0.0",
  "private": true,
  "engines": {
    "node": "7.10.2" // <-- This is too old, set it to the node version you are running locally (8.11.3)
  },

I hope this helps someone.

answered Sep 07 '18 at 18:46

Ian Ellis

541
6
19

1

This solved it for me. Downgraded from Node 10 to Node 8 and got my repo running locally. – Reece Daniels Jul 05 '19 at 08:38
I don't have anything like `"engines": { "node": "7.10.2"locally (8.11.3) },` in my package.json. Can't figure out what version of Node it think it is – John Jun 25 '21 at 08:51

score 15 · Answer 6 · answered Jan 25 '22 at 06:25

In my case, it was cased by node-sass(version < 6.0.1) not supporting Node 16. Update node-sass to 6.0.1 and the issue is solved. see error: no template named 'remove_cv_t' in namespace 'std'; did you mean 'remove_cv'?.

One learning to my experience is that you should read the error messages very carefully and search the "root cause message". In my case it was error: no template named 'remove_cv_t' in namespace 'std'; did you mean 'remove_cv'?. It showed right above the GYP ERR! build error. stack Error: 'make' failed with exit code 2 line.

andromeda · Answer 7 · 2019-09-30T07:34:30.637

9

Delete the ~/.node-gyp folder and then the ~/.npmrc file.

Reboot your server and rerun npm install in your project folder

Edit:

Warning: removing ~/.npmrc will delete your other configurations

edited Sep 30 '19 at 07:34

answered Jul 24 '18 at 18:12

andromeda

4,433
5
32
42

3

Warning: removing `~/.npmrc` will delete your other configurations, for example your default author name. – Paul Razvan Berg Sep 28 '19 at 18:47

score 4 · Answer 8 · answered Sep 15 '19 at 08:08

I think delete this directory and clean the cache of npm is better:

rm -rf ~/.node-gyp/
rm -r node_modules/.bin/;
rm -r build/
npm cache clean

and you can test

npm install -g node-gyp

and

npm install -g node-pre-gyp

finally:

npm install <your module>

score 4 · Answer 9 · answered May 22 '22 at 07:40

4

In Linux it is fixed by installing build essential sudo apt-get install build-essential but in my Windows wsl2 installing only the build-essential did not solve the issue, I have to downgrade the node to 16.15.0 then it got resolved.

answered May 22 '22 at 07:40

Rajarshi Biswas

41
1

score 3 · Answer 10 · answered Apr 29 '21 at 17:18

3

I encountered this while building the image based on node:alipine.

Since my Dockerfile didn't specify the version, the latest one was used, which is Node 16 published 3 days ago at Docker Hub.

Downgrading it to 15 (node:15-alpine) solved the problem.

answered Apr 29 '21 at 17:18

Иван Бишевац

13,811
21
66
93

score 2 · Answer 11 · edited Jul 01 '20 at 11:50

2

If you are using NVM, you can also change to the version your package supports, like:

nvm install 7.10.2
nvm use 7.10.2

edited Jul 01 '20 at 11:50

vipulgupta2048

141
1
14

answered Apr 05 '19 at 20:30

Robinson Marquez

66
4

score 2 · Answer 12 · answered Aug 17 '22 at 09:38

2

change Node version from 16.15.1 to 14.17.3

 sudo n 14.17.3

answered Aug 17 '22 at 09:38

Ado

411
4
9

This worked for me. `npm install` failed in my project. I saw a recommendation to upgrade it and did it. I had npm 16.15.1. `npm install` failed again. Cleaning caches did not help. Downgrading npm and cleaning caches helped. Command I used `npm install -g node@14.17.3 --force` – kinORnirvana Jan 26 '23 at 16:24

TonyN96 · Answer 13 · 2023-02-13T15:31:33.320

I had the same problem, but didn't realise it was being caused by an error further up in the logs. python was not installed correctly.

env: python: No such file or directory
make: *** [Release/sass.a] Error 127
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/private/var/folders/5q/3y3xtdk11g11sgclgtc6vtvh0000gn/T/xfs-b4670056/node_modules/node-gyp/lib/build.js:194:23)

HAOBO LUO · Answer 14 · 2019-06-05T05:40:36.933

I got the same problem when installed the gazebo gzweb. I found out that apt install nodejs install the "node" in the direction of "/usr/bin/". You can verify by which node. But node -v is still referring to "/usr/local/bin/node" which is a wrong version I failed to uninstall. Thus as my solution:

rm -rf /usr/local/bin/node
cp -i /usr/bin/node /usr/local/bin/
cp -i /usr/bin/nodejs /usr/local/bin/

Steps:

sudo apt-get install npm npm install -g n n stable npm install npm@6.9.0 -g ln -s /usr/local/bin/npm /usr/bin/npm

score 0 · Answer 15 · answered Jan 27 '20 at 23:09

CentOS 6 users

Node 10+ requires GCC4.9. And apparently CentOS 6 doesn't have it. You can use these commands before npm install as a workaround (tested with Node 11 NPM 6).

yum install devtoolset-7
source scl_source enable devtoolset-7

Source: https://github.com/lovell/sharp/issues/1283

kheengz · Answer 16 · 2023-01-24T11:26:58.467

0

Follow these steps to resolve the issue.

Debug #1: Deleting package-lock.json file

rm -rf package-lock.json
rm -rf node_modules

npm install

Debug #2: Deleting .node-gyp folder

rm -rf ~/.node-gyp

npm install

Debug #3: Re-install node-gyp

npm i -g node-gyp

Debug #4: Install build essentials

sudo apt-get install -y build-essential

Source: https://codeforgeek.com/make-failed-with-exit-code-2/

edited Jan 24 '23 at 11:26

answered Apr 24 '20 at 10:02

kheengz

840
12
10

1

please update your answer with corresponding commands – Ram Jan 23 '23 at 14:23

score 0 · Answer 17 · edited Apr 13 '21 at 05:49

0

I am working on Ubuntu 20.04. I tried all the solutions mentioned here and nothing worked. The actual problem is versioning difference. I am sure the same package.json will be working fine on one of your team mate's local machine. You just need to ask your team mates about which npm and node version they are using and install it on your local machine.

To install specific version of npm:

sudo npm install -g npm@specific_npm_version_here

To install specific version of node:

sudo npm install -g n
sudo n specify_node_version_here

edited Apr 13 '21 at 05:49

David Buck

3,752
35
31
35

answered Apr 13 '21 at 05:13

Saket Suraj

165
1
2
10

Please don't post the same answer to multiple questions. They will get flagged for deletion and, if multiple questions have the same answer you should consider flagging those questions as duplicates rather than repeating your answer. – David Buck Apr 13 '21 at 05:53
@DavidBuck Thanks for pointing this out. I was not aware of it. The motive is to provide correct solution. – Saket Suraj Apr 13 '21 at 07:05
Understood. [This answer](https://meta.stackoverflow.com/a/292331/7508700) has some helpful advice. – David Buck Apr 13 '21 at 07:23

score 0 · Answer 18 · answered Jan 08 '22 at 08:54

If you're reading this after December 16th 2021, you may have been seeing build errors due to a Heroku node version upgrade issue.

As per the Heroku changelog:

Ruby apps now default to Node version 16.13.1 and Yarn version 1.22.17 Change effective on 16 December 2021

Applications using the heroku/ruby buildpack that do not have a version of Node installed by another buildpack (such as the heroku/nodejs buildpack) will now receive:

Node version 16.13.1 (was previously 12.16.2) Yarn version 1.22.17 (was previously 1.22.4)

https://devcenter.heroku.com/changelog-items/2306

score 0 · Answer 19 · answered May 11 '22 at 02:18

0

i had the same error, and for me the solution was to downgrade the node version.

answered May 11 '22 at 02:18

alycecristines

400
2
9

score 0 · Answer 20 · answered Sep 14 '22 at 15:21

0

Sometimes the project depends on older node version. Ask the owner about appropriate version or make a try with 'nvm install

answered Sep 14 '22 at 15:21

Pham Duc Toan

149
1
3