Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

(node-gyp rebuild 2> builderror.log) || (exit 0)

See original GitHub issue

# npm install socket.io
npm http GET https://registry.npmjs.org/socket.io
npm http 304 https://registry.npmjs.org/socket.io
npm http GET https://registry.npmjs.org/base64id/0.1.0
npm http GET https://registry.npmjs.org/redis/0.7.3
npm http GET https://registry.npmjs.org/socket.io-client/0.9.11
npm http GET https://registry.npmjs.org/policyfile/0.0.4
npm http 304 https://registry.npmjs.org/base64id/0.1.0
npm http 304 https://registry.npmjs.org/redis/0.7.3
npm http 304 https://registry.npmjs.org/policyfile/0.0.4
npm http 304 https://registry.npmjs.org/socket.io-client/0.9.11
npm http GET https://registry.npmjs.org/xmlhttprequest/1.4.2
npm http GET https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http GET https://registry.npmjs.org/uglify-js/1.2.5
npm http GET https://registry.npmjs.org/ws
npm http 304 https://registry.npmjs.org/xmlhttprequest/1.4.2
npm http 304 https://registry.npmjs.org/ws
npm http 304 https://registry.npmjs.org/active-x-obfuscator/0.0.1
npm http 304 https://registry.npmjs.org/uglify-js/1.2.5
npm http GET https://registry.npmjs.org/zeparser/0.0.5
npm http GET https://registry.npmjs.org/options
npm http GET https://registry.npmjs.org/tinycolor
npm http GET https://registry.npmjs.org/commander
npm http 304 https://registry.npmjs.org/zeparser/0.0.5
npm http 304 https://registry.npmjs.org/options
npm http 304 https://registry.npmjs.org/tinycolor
npm http 304 https://registry.npmjs.org/commander

> ws@0.4.25 install /root/node_modules/socket.io/node_modules/socket.io-client/node_modules/ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)

socket.io@0.9.13 node_modules/socket.io
├── base64id@0.1.0
├── policyfile@0.0.4
├── redis@0.7.3
└── socket.io-client@0.9.11 (xmlhttprequest@1.4.2, uglify-js@1.2.5, ws@0.4.25, active-x-obfuscator@0.0.1)

Issue Analytics

State:
Created 11 years ago
Comments:26 (4 by maintainers)

Top GitHub Comments

2reactions

ghostcommented, Feb 23, 2013

Hack Trick work:

# cd ~
# npm install -g node-gyp
# npm install socket.io

https://github.com/TooTallNate/node-gyp#readme

0reactions

ghostcommented, Mar 22, 2015

on ubuntu 14.04 I needed to create a link in /usr/bin because /usr/bin/env was looking for /usr/bin/node

ln -s /usr/bin/nodejs /usr/bin/node

Top Results From Across the Web

(node-gyp rebuild 2> builderror.log) || (exit 0)

nothing seems to work. I used to have sails up and running on my machine untill I uninstalled it. Now that I want...

npm build error "node-gyp rebuild" error (#2768) - GitLab

gyp: Call to 'node -p "require('node-addon-api').include"' returned exit status 0 while in binding.gyp. while trying to load binding.gyp gyp ...

error with heapdump while installing strongloop

I am getting following error with heapdump while installing strongloop. has anyone encountered this error? > heap...@0.2.10 install D:\nodejs\node_modules\ ...

Npm install command failing with message "could not find ...

But then, suddenly, it stops with the error: npm ERR! code 1 npm ERR! ... command C:\Windows\system32\cmd.exe /d /s /c node-gyp rebuild npm ......

Pipeline break in node-gyp rebuild

we get gyp ERR! build error gyp ERR! stack Error: `make` failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit.