question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

gyp and bignum error during installation on Debian

See original GitHub issue

I am trying to install homebridge on debian on my Dragonboard 410c (raspberry pi alternative) using npm install -g homebridge. However, I keep running into the following error pasted below. I have already installed nodejs-legacy.

npm WARN excluding symbolic link utils/ncov -> lib/ncov.js \

curve25519@1.1.0 install /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/curve25519 node-gyp rebuild

(node) child_process: options.customFds option is deprecated. Use options.stdio instead. make: Entering directory ‘/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/curve25519/build’ CXX(target) Release/obj.target/curve/node_curve.o SOLINK_MODULE(target) Release/obj.target/curve.node COPY Release/curve.node make: Leaving directory ‘/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/curve25519/build’ npm WARN excluding symbolic link utils/ncov -> lib/ncov.js

bignum@0.11.0 install /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/srp/node_modules/bignum node-gyp configure build

(node) child_process: options.customFds option is deprecated. Use options.stdio instead. gyp: Undefined variable openssl_config_path in binding.gyp gyp ERR! configure error gyp ERR! stack Error: gyp failed with exit code: 1 gyp ERR! stack at ChildProcess.onCpExit (/usr/share/node-gyp/lib/configure.js:344:16) gyp ERR! stack at emitTwo (events.js:87:13) gyp ERR! stack at ChildProcess.emit (events.js:172:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12) gyp ERR! System Linux 4.4.0-linaro-lt-qcom gyp ERR! command “/usr/bin/nodejs” “/usr/bin/node-gyp” “configure” “build” gyp ERR! cwd /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/srp/node_modules/bignum gyp ERR! node -v v4.2.2 gyp ERR! node-gyp -v v0.12.2 gyp ERR! not ok npm WARN This failure might be due to the use of legacy binary “node” npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian

mdns@2.2.11 install /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/mdns node-gyp rebuild

path.js:424 var path = (i >= 0) ? arguments[i] : process.cwd(); ^

Error: ENOENT: no such file or directory, uv_cwd at Error (native) at Object.posix.resolve (path.js:424:50) at Function.Module._resolveLookupPaths (module.js:249:17) at Function.Module._resolveFilename (module.js:327:31) at Function.Module._load (module.js:287:25) at Module.require (module.js:366:17) at require (module.js:385:17) at Object.<anonymous> (/usr/share/node-gyp/bin/node-gyp.js:13:11) at Module._compile (module.js:435:26) at Object.Module._extensions…js (module.js:442:10) npm ERR! bignum@0.11.0 install: node-gyp configure build npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the bignum@0.11.0 install script. npm ERR! This is most likely a problem with the bignum package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-gyp configure build npm ERR! You can get their info via: npm ERR! npm owner ls bignum npm ERR! There is likely additional logging output above. npm ERR! System Linux 4.4.0-linaro-lt-qcom npm ERR! command “/usr/bin/nodejs” “/usr/bin/npm” “install” “-g” “homebridge” npm ERR! cwd /home/linaro npm ERR! node -v v4.2.2 npm ERR! npm -v 1.4.21 npm ERR! code ELIFECYCLE npm WARN This failure might be due to the use of legacy binary “node” npm WARN For further explanations, please read /usr/share/doc/nodejs/README.Debian

ed25519@0.0.3 install /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/node_modules/ed25519 node-gyp rebuild

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:18 (3 by maintainers)

github_iconTop GitHub Comments

8reactions
Connor-Knabecommented, Apr 1, 2016

This seemed to fix it for me sudo apt-get install libavahi-compat-libdnssd-dev

0reactions
scommacommented, Feb 5, 2018

I got the same error message as OP (@Nedervino) and this issue was among a few real search results. It happens because your working directory no longer exists. Just cd ~ and run whatever you were trying to run again.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Developers - gyp and bignum error during installation on Debian -
I am trying to install homebridge on debian on my Dragonboard 410c (raspberry pi alternative) using npm install -g homebridge. However, I keep...
Read more >
sudo npm install bignum -g : OSError - node.js - Stack Overflow
Im getting this error when try to install bignum . System info: nodejs PPA ppa:chris-lea/node.js. node -v v0.10.26. npm -v 1.4.3.
Read more >
bignum - npm
Start using bignum in your project by running `npm i bignum`. ... This library is based on node-bigint by substack, but instead of...
Read more >
equihash-solomining/Lobby - Gitter
npm ERR! npm ERR! Failed at the bignum@0.12.5 install script. npm ERR! This is probably not a problem with npm. There is likely...
Read more >
npm update fails with cryptonote - Server Fault
npm bignum requires Python version 2.7 installed. Found out from another poster that Python 3+ does not run some functions in my libraries....
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found