Open karolyi opened 10 years ago
also, this: https://github.com/rvagg/nan
Just hit this same error (well at least the first screenfull is identical) in Ubuntu 12.04 ARM (BBB) with node v0.11.14-pre. Tried both the npm install and the Git clone. Looks to me like the gyp included here is way old:
ubuntu@ubuntu-armhf:~/Ldrv/memwatch$ npm outdated
npm http GET https://registry.npmjs.org/mocha
npm http GET https://registry.npmjs.org/should
npm http GET https://registry.npmjs.org/node-gyp
npm http 304 https://registry.npmjs.org/should
npm http 304 https://registry.npmjs.org/mocha
npm http 304 https://registry.npmjs.org/node-gyp
Package Current Wanted Latest Location
should 0.6.3 0.6.3 4.0.4 should
mocha 1.2.2 1.2.2 1.20.1 mocha
node-gyp 0.5.7 0.5.7 0.13.1 node-gyp
ubuntu@ubuntu-armhf:~/Ldrv/memwatch$
I've been able to get past this in other packages by forcing use of a new gyp, but when there are other outdated packages it just gets to be too much hassle. Am I missing some easy way to work around this?
Could we get a version that includes the current node-gyp?
added v0.11 support in this PR #56 :)
I'm still getting this issue
I get this issue. Output:
gyp ERR! build error
gyp ERR! stack Error: not found: make
gyp ERR! stack at F (/usr/lib/node_modules/npm/node_modules/which/which.js:43:28)
gyp ERR! stack at E (/usr/lib/node_modules/npm/node_modules/which/which.js:46:29)
gyp ERR! stack at /usr/lib/node_modules/npm/node_modules/which/which.js:57:16
gyp ERR! stack at Object.oncomplete (evalmachine.<anonymous>:107:15)
gyp ERR! System Linux 3.11.0-12-generic
gyp ERR! command "node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /usr/lib/node_modules/memwatch
gyp ERR! node -v v0.10.32
gyp ERR! node-gyp -v v1.0.1
gyp ERR! not ok
npm ERR! memwatch@0.2.2 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the memwatch@0.2.2 install script.
npm ERR! This is most likely a problem with the memwatch 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 memwatch
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.11.0-12-generic
npm ERR! command "/usr/bin/node" "/usr/bin/npm" "install" "-g" "memwatch"
npm ERR! cwd /tmp/dpd/deployd
npm ERR! node -v v0.10.32
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR! not ok code 0
@jpgcc use the PR mentioned above for node 0.11 support (https://github.com/lloyd/node-memwatch/pull/56)
memwatch doesn't seem to be maintained anymore. Last commit was 2 years ago and PRs & issues are not addressed. Perhaps it's time to look for a replacement.
@tjfontaine - did as you requested at #noderoad and tried 0.11.14. This issue seems to be what is restricting myself and others from moving 0.10 --> 0.11.
I guess we can remove memwatch, though.
I suggest you look into this, might be an easy fix: https://github.com/dainis/node-gcstats/issues/1