Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- machine:finixDLT douglas$ npm install hfc
- npm WARN deprecated crypto@0.0.3: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in.
- npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
- > hashtable@2.0.2 install /Users/douglas/finixDLT/node_modules/hashtable
- > node-gyp configure build
- CXX(target) Release/obj.target/native/src/hashtable.o
- In file included from ../src/hashtable.cpp:1:
- ../src/hashtable.h:7:10: fatal error: 'tr1/unordered_map' file not found
- #include <tr1/unordered_map>
- ^~~~~~~~~~~~~~~~~~~
- 1 error generated.
- make: *** [Release/obj.target/native/src/hashtable.o] Error 1
- gyp ERR! build error
- gyp ERR! stack Error: `make` failed with exit code: 2
- gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:258:23)
- gyp ERR! stack at ChildProcess.emit (events.js:159:13)
- gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:12)
- gyp ERR! System Darwin 17.3.0
- gyp ERR! command "/usr/local/Cellar/node/9.3.0_1/bin/node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "configure" "build"
- gyp ERR! cwd /Users/douglas/finixDLT/node_modules/hashtable
- gyp ERR! node -v v9.3.0
- gyp ERR! node-gyp -v v3.6.2
- gyp ERR! not ok
- npm WARN enoent ENOENT: no such file or directory, open '/Users/douglas/finixDLT/package.json'
- npm WARN ajv-keywords@3.0.0 requires a peer of ajv@^6.0.0 but none is installed. You must install peer dependencies yourself.
- npm WARN finixDLT No description
- npm WARN finixDLT No repository field.
- npm WARN finixDLT No README data
- npm WARN finixDLT No license field.
- npm ERR! code ELIFECYCLE
- npm ERR! errno 1
- npm ERR! hashtable@2.0.2 install: `node-gyp configure build`
- npm ERR! Exit status 1
- npm ERR!
- npm ERR! Failed at the hashtable@2.0.2 install script.
- npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
- npm ERR! A complete log of this run can be found in:
- npm ERR! /Users/douglas/.npm/_logs/2018-01-18T15_41_51_291Z-debug.log
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement