bitpay / node-bitpay-client

A Node.js module and command line client for interacting with BitPay's Cryptographically Secure API
102 stars 95 forks source link

node-gyp rebuild error #99

Open Sebastp opened 5 years ago

Sebastp commented 5 years ago

This package depends on the old version of secp256k1. This throws an error on Windows '.' is not recognized as an internal or external command, operable program or batch file. gyp: Call to './utils/has_lib.sh gmpxx && ./utils/has_lib.sh gmp' returned exit status 1 while in binding.gyp. while trying to load binding.gyp gyp ERR! configure error gyp ERR! stack Error: gyp failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (C:\Users\Sebastian\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\configure.js:345:16) gyp ERR! stack at ChildProcess.emit (events.js:160:13) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:12) gyp ERR! System Windows_NT 6.3.9600 gyp ERR! command "C:\Program Files\nodejs\node.exe" "C:\Users\Sebastian\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuild" gyp ERR! cwd C:\xampp\htdocs\RoyaleCase\server\node_modules\secp256k1 gyp ERR! node -v v9.4.0 gyp ERR! node-gyp -v v3.8.0 gyp ERR! not ok npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! secp256k1@1.1.5 install: node-gyp rebuild npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the secp256k1@1.1.5 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\Sebastian\AppData\Roaming\npm-cache_logs\2018-11-07T21_34_50_763Z-debug.log

Please fix this or specify system requirements

SebastienGras commented 5 years ago

+1

superdev2020 commented 5 years ago

Same issue. How can I solve it?

mirillis commented 5 years ago

9 months later still no response or fix... pity.

rodrigooler commented 4 years ago

Has anyone managed to solve this problem?

86667 commented 4 years ago

Temporary solve by downgrading Node version.

https://github.com/bitpay/copay/issues/8243