-
Notifications
You must be signed in to change notification settings - Fork 35
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
NPM not working.. How to install? #32
Comments
wow that is a bad bug report. I would hate to get one like that. Anyway, I also have an issue install hashlib with npm. I'm trying to install 'webshell', which relies on hashlib. The hashlib dependency fails, however. If I try to do the manual install (following the instructions in the readme) it does work, but npm isn't aware of it and tries to install the (failing) hashlib dependency anywhay. Here is the output I'm getting:
|
Getting the same issue with Node v0.6.15 on both CentOS 5.8 and Fedora 16. Here's my trace: [root@localhost node]# npm install hashlib
npm http GET https://registry.npmjs.org/hashlib
npm http 304 https://registry.npmjs.org/hashlib
> hashlib@1.0.1 preinstall /root/node/node_modules/hashlib
> node-waf clean || (exit 0); node-waf configure build
Nothing to clean (project not configured)
Checking for program g++ or c++ : /usr/bin/g++
Checking for program cpp : /usr/bin/cpp
Checking for program ar : /usr/bin/ar
Checking for program ranlib : /usr/bin/ranlib
Checking for g++ : ok
Checking for program gcc or cc : /usr/bin/gcc
Checking for program ar : /usr/bin/ar
Checking for program ranlib : /usr/bin/ranlib
Checking for gcc : ok
Checking for node path : not found
Checking for node prefix : ok /usr
'configure' finished successfully (0.081s)
Waf: Entering directory `/root/node/node_modules/hashlib/build'
[1/6] cc: libhash/md4c.c -> build/Release/libhash/md4c_1.o
[2/6] cc: libhash/md5c.c -> build/Release/libhash/md5c_1.o
[3/6] cc: libhash/sha0c.c -> build/Release/libhash/sha0c_1.o
[4/6] cxx: hashlib.cc -> build/Release/hashlib_2.o
../hashlib.cc:14:16: error: ev.h: No such file or directory
../hashlib.cc:15:17: error: eio.h: No such file or directory
../hashlib.cc:311: error: ‘eio_req’ was not declared in this scope
../hashlib.cc:311: error: ‘req’ was not declared in this scope
../hashlib.cc:312: error: expected ‘,’ or ‘;’ before ‘{’ token
Waf: Leaving directory `/root/node/node_modules/hashlib/build'
Build failed: -> task failed (err #1):
{task: cxx hashlib.cc -> hashlib_2.o}
npm ERR! hashlib@1.0.1 preinstall: `node-waf clean || (exit 0); node-waf configure build`
npm ERR! `sh "-c" "node-waf clean || (exit 0); node-waf configure build"` failed with 1
npm ERR!
npm ERR! Failed at the hashlib@1.0.1 preinstall script.
npm ERR! This is most likely a problem with the hashlib package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-waf clean || (exit 0); node-waf configure build
npm ERR! You can get their info via:
npm ERR! npm owner ls hashlib
npm ERR! There is likely additional logging output above.
npm ERR!
npm ERR! System Linux 2.6.18-274.18.1.el5
npm ERR! command "nodejs" "/usr/bin/npm" "install" "hashlib"
npm ERR! cwd /root/node
npm ERR! node -v v0.6.15
npm ERR! npm -v 1.1.18
npm ERR! code ELIFECYCLE
npm ERR! message hashlib@1.0.1 preinstall: `node-waf clean || (exit 0); node-waf configure build`
npm ERR! message `sh "-c" "node-waf clean || (exit 0); node-waf configure build"` failed with 1
npm ERR! errno {}
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /root/node/npm-debug.log
npm not ok |
bump |
Getting similar on OSX sudoed, when installing as a dependency for: https://github.com/zsolt/retwis-nodejs Log: Any update on this, as performant hashing is pretty important. |
Same on last ubuntu:
|
TEH SAEM!111 |
I have the same problem, maybe it is because node-waf is an external tool that now is deprecated. can you please try to use node-gyp ? |
sorry, have no time to support it at the moment |
NPM not working.. How to install?
The text was updated successfully, but these errors were encountered: