vkupar
commented
6 years ago I installed node 0.10.29 and it seems solved.
Closed vkupar closed 6 years ago
vkupar
commented
6 years ago I installed node 0.10.29 and it seems solved.
I followed these steps: git clone https://github.com/electroneum/electroneum-pool.git pool cd pool npm update
When I run "npm update", then error occured. I tried with sudo and without sudo (with regular user) but still error.
System: Ubuntu server 16.04.3 LTS Node.js: v0.10.48
I used this guide too, but nothing solves: http://betbybitcoin.com/setup-electroneumetn-mining-pool/
Whole log:
root@server:/home/user/pool# npm update redis@0.12.1 node_modules/redis async@1.5.2 node_modules/async npm WARN engine request@2.81.0: wanted: {"node":">= 4"} (current: {"node":"0.10.48","npm":"2.15.1"}) npm WARN engine request@2.81.0: wanted: {"node":">= 4"} (current: {"node":"0.10.48","npm":"2.15.1"}) npm WARN engine deep-extend@0.4.2: wanted: {"node":">=0.12.0","iojs":">=1.0.0"} (current: {"node":"0.10.48","npm":"2.15.1"}) npm WARN engine deep-extend@0.4.2: wanted: {"node":">=0.12.0","iojs":">=1.0.0"} (current: {"node":"0.10.48","npm":"2.15.1"}) npm WARN engine form-data@2.1.4: wanted: {"node":">= 0.12"} (current: {"node":"0.10.48","npm":"2.15.1"}) npm WARN engine har-validator@4.2.1: wanted: {"node":">=4"} (current: {"node":"0.10.48","npm":"2.15.1"}) npm WARN engine form-data@2.1.4: wanted: {"node":">= 0.12"} (current: {"node":"0.10.48","npm":"2.15.1"}) npm WARN engine har-validator@4.2.1: wanted: {"node":">=4"} (current: {"node":"0.10.48","npm":"2.15.1"}) dateformat@1.0.12 node_modules/dateformat ├── get-stdin@4.0.1 └── meow@3.7.0 (map-obj@1.0.1, trim-newlines@1.0.0, decamelize@1.2.0, object-assign@4.1.1, minimist@1.2.0, camelcase-keys@2.1.0, loud-rejection@1.6.0, normalize-package-data@2.4.0, redent@1.0.0, read-pkg-up@1.0.1) npm WARN engine har-schema@1.0.5: wanted: {"node":">=4"} (current: {"node":"0.10.48","npm":"2.15.1"}) npm WARN engine har-schema@1.0.5: wanted: {"node":">=4"} (current: {"node":"0.10.48","npm":"2.15.1"}) npm WARN engine co@4.6.0: wanted: {"iojs":">= 1.0.0","node":">= 0.12.0"} (current: {"node":"0.10.48","npm":"2.15.1"}) npm WARN engine co@4.6.0: wanted: {"iojs":">= 1.0.0","node":">= 0.12.0"} (current: {"node":"0.10.48","npm":"2.15.1"})
cli-color@1.1.0 node_modules/cli-color ├── ansi-regex@2.1.1 ├── d@0.1.1 ├── timers-ext@0.1.2 (next-tick@1.0.0) ├── es6-iterator@2.0.3 (d@1.0.0, es6-symbol@3.1.1) ├── memoizee@0.3.10 (lru-queue@0.1.0, next-tick@0.2.2, event-emitter@0.3.5, es6-weak-map@0.1.4) └── es5-ext@0.10.37 (es6-symbol@3.1.1) [bignum] Success: "/home/user/pool/node_modules/base58-native/node_modules/bignum/binding/bignum.node" is installed via remote
base58-native@0.1.4 node_modules/base58-native └── bignum@0.12.5 (nan@2.8.0, node-pre-gyp@0.6.39) [bignum] Success: "/home/user/pool/node_modules/bignum/binding/bignum.node" is installed via remote
make: Entering directory '/home/user/pool/node_modules/cryptonote-util/build' CXX(target) Release/obj.target/cryptonote/src/main.o bignum@0.12.5 node_modules/bignum ├── nan@2.8.0 └── node-pre-gyp@0.6.39 (detect-libc@1.0.3, semver@5.4.1, rc@1.2.2, mkdirp@0.5.1, nopt@4.0.1, npmlog@4.1.2, tar-pack@3.4.1, rimraf@2.6.2, tar@2.2.1, hawk@3.1.3, request@2.81.0) CXX(target) Release/obj.target/cryptonote/src/cryptonote_core/cryptonote_format_utils.o ../src/cryptonote_core/cryptonote_format_utils.cpp: In function ‘bool cryptonote::check_proof_of_work(const cryptonote::block&, cryptonote::difficulty_type, crypto::hash&)’: ../src/cryptonote_core/cryptonote_format_utils.cpp:938:3: warning: no return statement in function returning non-void [-Wreturn-type] } ^ CC(target) Release/obj.target/cryptonote/src/crypto/tree-hash.o CXX(target) Release/obj.target/cryptonote/src/crypto/crypto.o CC(target) Release/obj.target/cryptonote/src/crypto/crypto-ops.o CC(target) Release/obj.target/cryptonote/src/crypto/crypto-ops-data.o CC(target) Release/obj.target/cryptonote/src/crypto/hash.o CC(target) Release/obj.target/cryptonote/src/crypto/keccak.o CXX(target) Release/obj.target/cryptonote/src/common/base58.o SOLINK_MODULE(target) Release/obj.target/cryptonote.node COPY Release/cryptonote.node make: Leaving directory '/home/user/pool/node_modules/cryptonote-util/build'
make: Entering directory '/home/user/pool/node_modules/multi-hashing/build' CXX(target) Release/obj.target/multihashing/multihashing.o ../multihashing.cc:23:22: warning: extra tokens at end of #include directive
include "sha1.h",
../multihashing.cc: In function ‘v8::Handle except(const char)’:
../multihashing.cc:34:44: error: ‘New’ is not a member of ‘v8::String’
return ThrowException(Exception::Error(String::New(msg)));
^
../multihashing.cc:34:61: error: ‘ThrowException’ was not declared in this scope
return ThrowException(Exception::Error(String::New(msg)));
^
../multihashing.cc: At global scope:
../multihashing.cc:37:27: error: ‘Arguments’ does not name a type
Handle quark(const Arguments& args) {
^
In file included from /usr/include/nodejs/src/node.h:42:0,
from ../multihashing.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h: In function ‘v8::Handle quark(const int&)’:
/usr/include/nodejs/deps/v8/include/v8.h:885:13: error: ‘v8::HandleScope::HandleScope()’ is protected
V8_INLINE HandleScope() {}
^
../multihashing.cc:38:17: error: within this context
HandleScope scope;
^
../multihashing.cc:40:14: error: request for member ‘Length’ in ‘args’, which is of non-class type ‘const int’
if (args.Length() < 1)
^
../multihashing.cc:43:34: error: invalid types ‘const int[int]’ for array subscript
Local ’ token
Buffer buff = Buffer::New(output, 32);
^
../multihashing.cc:55:13: error: ‘buff’ was not declared in this scope
Buffer buff = Buffer::New(output, 32);
^
../multihashing.cc:55:42: error: no matching function for call to ‘New(char [32], int)’
Buffer buff = Buffer::New(output, 32);
^
In file included from ../multihashing.cc:2:0:
/usr/include/nodejs/src/node_buffer.h:28:40: note: candidate: v8::MaybeLocal node::Buffer::New(v8::Isolate , size_t)
NODE_EXTERN v8::MaybeLocal New(v8::Isolate isolate, size_t length);
^
/usr/include/nodejs/src/node_buffer.h:28:40: note: no known conversion for argument 1 from ‘char [32]’ to ‘v8::Isolate’
/usr/include/nodejs/src/node_buffer.h:31:40: note: candidate: v8::MaybeLocal node::Buffer::New(v8::Isolate, v8::Local, node::encoding)
NODE_EXTERN v8::MaybeLocal New(v8::Isolate isolate,
^
/usr/include/nodejs/src/node_buffer.h:31:40: note: no known conversion for argument 1 from ‘char [32]’ to ‘v8::Isolate’
/usr/include/nodejs/src/node_buffer.h:36:40: note: candidate: v8::MaybeLocal node::Buffer::New(v8::Isolate , char, size_t, node::Buffer::FreeCallback, void)
NODE_EXTERN v8::MaybeLocal New(v8::Isolate isolate,
^
/usr/include/nodejs/src/node_buffer.h:36:40: note: candidate expects 5 arguments, 2 provided
/usr/include/nodejs/src/node_buffer.h:43:40: note: candidate: v8::MaybeLocal node::Buffer::New(v8::Isolate , char, size_t)
NODE_EXTERN v8::MaybeLocal New(v8::Isolate isolate,
^
/usr/include/nodejs/src/nodebuffer.h:43:40: note: candidate expects 3 arguments, 2 provided
../multihashing.cc:56:18: error: ‘class v8::HandleScope’ has no member named ‘Close’
return scope.Close(buff->handle);
^
../multihashing.cc: At global scope:
../multihashing.cc:59:25: error: ‘Arguments’ does not name a type
Handle x11(const Arguments& args) {
^
In file included from /usr/include/nodejs/src/node.h:42:0,
from ../multihashing.cc:1:
/usr/include/nodejs/deps/v8/include/v8.h: In function ‘v8::Handle x11(const int&)’:
/usr/include/nodejs/deps/v8/include/v8.h:885:13: error: ‘v8::HandleScope::HandleScope()’ is protected
V8_INLINE HandleScope() {}
^
../multihashing.cc:60:17: error: within this context
HandleScope scope;
^
../multihashing.cc:62:14: error: request for member ‘Length’ in ‘args’, which is of non-class type ‘const int’
if (args.Length() < 1)
^
../multihashing.cc:65:34: error: invalid types ‘const int[int]’ for array subscript
Local
npm ERR! multi-hashing@0.0.9 install:
node-gyp rebuildnpm ERR! Exit status 1 npm ERR! npm ERR! Failed at the multi-hashing@0.0.9 install script 'node-gyp rebuild'. npm ERR! This is most likely a problem with the multi-hashing 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 information on how to open an issue for this project with: npm ERR! npm bugs multi-hashing npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm ERR! npm owner ls multi-hashing npm ERR! There is likely additional logging output above.npm ERR! Please include the following file with any support request: npm ERR! /home/user/pool/npm-debug.log root@server:/home/user/pool#