node-threads-a-gogo2 icon indicating copy to clipboard operation
node-threads-a-gogo2 copied to clipboard

Install error!

Open BruceAn1978 opened this issue 6 years ago • 0 comments

Command: npm install tagg2

Errors:

[email protected] preinstall E:\electron\hello-world\node_modules\tagg2 node install.js

###########################################

thanks for choose tagg2 module to let node.js have multi threads functionally tagg2 module support windows, linux, mac,make sure nodejs version must >=0.8.x

if have any problem, Contact me

qq:53822985,email:[email protected]

so enjoy it!

###########################################

[email protected] install E:\electron\hello-world\node_modules\tagg2 node-gyp rebuild

E:\electron\hello-world\node_modules\tagg2>if not defined npm_config_node_gyp (node "D:\Node.js\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\....\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "D:\Node.js\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild ) gyp ERR! configure error gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable. gyp ERR! stack at PythonFinder.failNoPython (D:\Node.js\node_modules\npm\node_modules\node-gyp\lib\configure.js:483:19) gyp ERR! stack at PythonFinder. (D:\Node.js\node_modules\npm\node_modules\node-gyp\lib\configure.js:508:16) gyp ERR! stack at D:\Node.js\node_modules\npm\node_modules\graceful-fs\polyfills.js:284:29 gyp ERR! stack at FSReqWrap.oncomplete (fs.js:149:21) gyp ERR! System Windows_NT 10.0.10586 gyp ERR! command "D:\Node.js\node.exe" "D:\Node.js\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild" gyp ERR! cwd E:\electron\hello-world\node_modules\tagg2 gyp ERR! node -v v10.0.0 gyp ERR! node-gyp -v v3.6.2 gyp ERR! not ok npm WARN [email protected] No repository field.

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] install: node-gyp rebuild npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the [email protected] 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! C:\Users\Bob.An\AppData\Roaming\npm-cache_logs\2018-05-16T10_26_37_164Z-debug.log

BruceAn1978 avatar May 16 '18 10:05 BruceAn1978