Skip to content
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

Does not support on node.js v.0.12 #62

Closed
smartmouse opened this issue Mar 8, 2015 · 24 comments
Closed

Does not support on node.js v.0.12 #62

smartmouse opened this issue Mar 8, 2015 · 24 comments

Comments

@smartmouse
Copy link

npm WARN package.json [email protected] querystring is also the name of a node core module.
/

[email protected] install /home/bot/test/node_modules/memwatch
node-gyp rebuild

child_process: customFds option is deprecated, use stdio instead.
make: Entering directory /home/bot/test/node_modules/memwatch/build' CXX(target) Release/obj.target/memwatch/src/heapdiff.o In file included from ../src/heapdiff.cc:5: ../src/heapdiff.hh:15: error: expected class-name before ‘{’ token ../src/heapdiff.hh:19: error: expected unqualified-id before ‘&’ token ../src/heapdiff.hh:19: error: expected ‘)’ before ‘&’ token ../src/heapdiff.hh:19: error: expected ‘;’ before ‘&’ token ../src/heapdiff.hh:20: error: expected unqualified-id before ‘&’ token ../src/heapdiff.hh:20: error: expected ‘)’ before ‘&’ token ../src/heapdiff.hh:20: error: expected ‘;’ before ‘&’ token ../src/heapdiff.cc: In constructor ‘heapdiff::HeapDiff::HeapDiff()’: ../src/heapdiff.cc:30: error: class ‘heapdiff::HeapDiff’ does not have any field named ‘ObjectWrap’ /home/bot/.node-gyp/0.12.0/deps/v8/include/v8.h: In static member function ‘static void heapdiff::HeapDiff::Initialize(v8::Handle<v8::Object>)’: /home/bot/.node-gyp/0.12.0/deps/v8/include/v8.h:816: error: ‘v8::HandleScope::HandleScope()’ is protected ../src/heapdiff.cc:51: error: within this context ../src/heapdiff.cc:52: error: ‘New’ was not declared in this scope ../src/heapdiff.cc:54: error: ‘NewSymbol’ is not a member of ‘v8::String’ ../src/heapdiff.cc:56: error: ‘End’ was not declared in this scope ../src/heapdiff.cc:58: error: ‘NewSymbol’ is not a member of ‘v8::String’ ../src/heapdiff.cc: At global scope: ../src/heapdiff.cc:62: error: expected unqualified-id before ‘&’ token ../src/heapdiff.cc:62: error: expected ‘)’ before ‘&’ token ../src/heapdiff.cc:62: error: expected initializer before ‘&’ token ../src/heapdiff.cc:23: warning: ‘s_startTime’ defined but not used make: *** [Release/obj.target/memwatch/src/heapdiff.o] Error 1 make: Leaving directory/home/bot/test/node_modules/memwatch/build'
gyp ERR! build error
gyp ERR! stack Error: make failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/home/nodebot/IBMSVT32/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:268:23)
gyp ERR! stack at ChildProcess.emit (events.js:110:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:1067:12)
gyp ERR! System Linux 2.6.32-504.el6.ppc64
gyp ERR! command "node" "/home/nodebot/IBMSVT32/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/bot/test/node_modules/memwatch
gyp ERR! node -v v0.12.0
gyp ERR! node-gyp -v v1.0.2
gyp ERR! not ok
npm ERR! Linux 2.6.32-504.el6.ppc64
npm ERR! argv "/home/bot/T32/bin/node" "/home/bot/32/bin/npm" "install" "memwatch"
npm ERR! node v0.12.0
npm ERR! npm v2.5.1
npm ERR! code ELIFECYCLE

npm ERR! [email protected] install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] install script 'node-gyp rebuild'.
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.

@nmccready
Copy link

+1 needs c, c++ updates fun times

anko added a commit to anko/fountain that referenced this issue Mar 20, 2015
node-memwatch is kill for node 0.12 unless someone over at
lloyd/node-memwatch#62 does V8 update fun-times.

I realise this removes all the logging that would warn of impending
catastrophe, but that's how we roll, else we don't roll at all.
@francisdb
Copy link

see also #59

@joaomlneto
Copy link

Exactly same problem here. Only difference is I am on 'Linux 3.2.0-4-amd64'. :)

@jeffreydwalter
Copy link

Same problem on FreeBSD 10.0 with Node v0.12.0.

@dbellavista
Copy link

+1

1 similar comment
@murali4u45
Copy link

+1

@HolgerFrank
Copy link

+1

2 similar comments
@imrefazekas
Copy link

+1

@onury
Copy link

onury commented May 8, 2015

+1

@nmccready
Copy link

Move on to memwatch-next it works in v0.12.0 and iojs 2

@onury
Copy link

onury commented May 8, 2015

just did. thanks.

@cades
Copy link

cades commented May 18, 2015

+1

2 similar comments
@woss
Copy link

woss commented Jun 4, 2015

+1

@harishvadali
Copy link

+1

@ded
Copy link

ded commented Jun 8, 2015

so this module is useless without a fix. what's going on with this? who maintains this repo?

@francisdb
Copy link

@margaritis
Copy link

👍

2 similar comments
@ghost
Copy link

ghost commented Jun 22, 2015

+1

@mark-scott
Copy link

+1

@smartmouse
Copy link
Author

I just found a memwatch-next that will work with 0.1.2 node.js.
I think memwatch-next is the replacement of memwatch for 0.12 node.js
memwatch will only support 0.10.x node.js.

@pedro-lucas
Copy link

+1

1 similar comment
@roshangade
Copy link

+1

@ded
Copy link

ded commented Jul 27, 2015

ATTENTION ALL THOSE WHO READ UP TO THIS POINT!!!

It does not look like the maintainer is paying attention to this thread, but as it was pointed out, just use Memwatch-Next


@smartmouse
Copy link
Author

I am closing this one Now, so use memwatch-next now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests