jperkin / node-openzwave

node.js interface to libopenzwave
Other
110 stars 55 forks source link

Debian npm install failure #56

Closed amccool closed 8 years ago

amccool commented 8 years ago

have nodejs-legacy installed as well. node -v v4.1.0

openzwave.target.mk:104: recipe for target 'Release/obj.target/openzwave/src/openzwave.o' failed make: *\ [Release/obj.target/openzwave/src/openzwave.o] Error 1 make: Leaving directory '/root/node_modules/openzwave/build' gyp ERR! build error gyp ERR! stack Error: make failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/root/node_modules/node-gyp/lib/build.js:270:23) gyp ERR! stack at emitTwo (events.js:87:13) gyp ERR! stack at ChildProcess.emit (events.js:172:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12) gyp ERR! System Linux 4.1.0-2-686-pae gyp ERR! command "/usr/bin/nodejs" "/root/node_modules/.bin/node-gyp" "rebuild" gyp ERR! cwd /root/node_modules/openzwave gyp ERR! node -v v4.1.0 gyp ERR! node-gyp -v v3.0.3 gyp ERR! not ok npm WARN This failure might be due to the use of legacy binary "node" npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian

npm ERR! openzwave@0.0.33 install: node-gyp rebuild npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the openzwave@0.0.33 install script. npm ERR! This is most likely a problem with the openzwave package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-gyp rebuild npm ERR! You can get their info via: npm ERR! npm owner ls openzwave npm ERR! There is likely additional logging output above.

npm ERR! System Linux 4.1.0-2-686-pae npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "openzwave" npm ERR! cwd /root npm ERR! node -v v4.1.0 npm ERR! npm -v 1.4.21 npm ERR! code ELIFECYCLE npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /root/npm-debug.log npm ERR! not ok code 0

amccool commented 8 years ago

switched to v0.10 from nodesource, now I have a good compile and back to working.

https://nodesource.com/blog/nodejs-v012-iojs-and-the-nodesource-linux-repositories