search

RobbieClarken / node-epics

EPICS Channel Access for node.js
19 stars 10 forks source link

Error while installing on Ubuntu 14 #3

Closed dmichel76 closed 9 years ago

dmichel76 commented 9 years ago

Hi,

I just tried to install node-epics on a fresh Ubuntu 14.04 install by doing sudo apt-get install node npm npm install epics

but I get this error:

npm http GET https://registry.npmjs.org/epics npm http 304 https://registry.npmjs.org/epics npm http GET https://registry.npmjs.org/ref npm http GET https://registry.npmjs.org/ref-struct npm http GET https://registry.npmjs.org/ref-array npm http GET https://registry.npmjs.org/ffi npm http 304 https://registry.npmjs.org/ref npm http 304 https://registry.npmjs.org/ref-array npm http 304 https://registry.npmjs.org/ffi npm http 304 https://registry.npmjs.org/ref-struct npm http GET https://registry.npmjs.org/array-index npm http GET https://registry.npmjs.org/debug npm http 304 https://registry.npmjs.org/debug npm http 304 https://registry.npmjs.org/array-index npm http GET https://registry.npmjs.org/ms/0.6.2 npm http 304 https://registry.npmjs.org/ms/0.6.2 npm http GET https://registry.npmjs.org/bindings npm http GET https://registry.npmjs.org/nan npm http 304 https://registry.npmjs.org/nan npm http 304 https://registry.npmjs.org/bindings

ref@0.3.2 install /home/david/node_modules/epics/node_modules/ref node-gyp rebuild

gyp: Call to 'node -e "require('nan')"' returned exit status 1. while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: gyp failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:431:16) gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17) gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:797:12) gyp ERR! System Linux 3.13.0-37-generic gyp ERR! command "nodejs" "/usr/bin/node-gyp" "rebuild" gyp ERR! cwd /home/david/node_modules/epics/node_modules/ref gyp ERR! node -v v0.10.25 gyp ERR! node-gyp -v v0.10.10 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! Error: ENOENT, lstat '/home/david/node_modules/epics/node_modules/ffi/deps/libffi/testsuite/libffi.call/cls_4_1byte.c' npm ERR! If you need help, you may report this log at: npm ERR! http://github.com/isaacs/npm/issues npm ERR! or email it to: npm ERR! npm-@googlegroups.com

npm ERR! System Linux 3.13.0-37-generic npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install" "epics" npm ERR! cwd /home/david npm ERR! node -v v0.10.25 npm ERR! npm -v 1.3.10 npm ERR! path /home/david/node_modules/epics/node_modules/ffi/deps/libffi/testsuite/libffi.call/cls_4_1byte.c npm ERR! fstream_path /home/david/node_modules/epics/node_modules/ffi/deps/libffi/testsuite/libffi.call/cls_4_1byte.c npm ERR! fstream_type File npm ERR! fstream_class FileWriter npm ERR! code ENOENT npm ERR! errno 34 npm ERR! fstream_stack /usr/lib/nodejs/fstream/lib/writer.js:284:26 npm ERR! fstream_stack Object.oncomplete (fs.js:107:15) npm ERR! weird error 1 npm ERR! npm ERR! Additional logging details can be found in: npm ERR! /home/david/npm-debug.log npm ERR! not ok code 0

Any idea what is happening and how to solve it?

elstanto commented 9 years ago

Try installing nodejs-legacy and running again. If it works then the error is because of the rename of node to nodejs in Debian.

RobbieClarken commented 9 years ago

Yes, the problem is apt-get on Ubuntu and Debian installs node to /usr/bin/nodejs instead of /usr/bin/node. This can be fixed by running:

sudo apt-get install nodejs-legacy

Please let me know if you have any other issues.