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.

node-gyp rebuild error

See original GitHub issue
/usr/local/lib/node_modules# node-gyp rebuild


gyp info it worked if it ends with ok
gyp info using node-gyp@0.5.7
gyp info using node@0.8.1
gyp info spawn python
gyp info spawn args [ '/root/.node-gyp/0.8.1/tools/gyp_addon',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-I/usr/local/lib/node_modules/build/config.gypi',
gyp info spawn args   '-f',
gyp info spawn args   'make' ]
Traceback (most recent call last):
  File "/root/.node-gyp/0.8.1/tools/gyp_addon", line 38, in <module>
    rc = gyp.main(gyp_args)
  File "/root/.node-gyp/0.8.1/tools/gyp/pylib/gyp/__init__.py", line 471, in main
    options.circular_check)
  File "/root/.node-gyp/0.8.1/tools/gyp/pylib/gyp/__init__.py", line 111, in Load
    depth, generator_input_info, check, circular_check)
  File "/root/.node-gyp/0.8.1/tools/gyp/pylib/gyp/input.py", line 2289, in Load
    depth, check)
  File "/root/.node-gyp/0.8.1/tools/gyp/pylib/gyp/input.py", line 361, in LoadTargetBuildFile
    includes, True, check)
  File "/root/.node-gyp/0.8.1/tools/gyp/pylib/gyp/input.py", line 208, in LoadOneBuildFile
    raise Exception("%s not found (cwd: %s)" % (build_file_path, os.getcwd()))
Exception: binding.gyp not found (cwd: /usr/local/lib/node_modules) while trying to load binding.gyp
gyp ERR! rebuild error Error: `gyp_addon` failed with exit code: 1
gyp ERR! rebuild error     at ChildProcess.onCpExit (/usr/local/lib/node_modules/node-gyp/lib/configure.js:290:16)
gyp ERR! rebuild error     at ChildProcess.EventEmitter.emit (events.js:91:17)
gyp ERR! rebuild error     at Process._handle.onexit (child_process.js:674:10)
gyp ERR! not ok 

Issue Analytics

  • State:closed
  • Created 11 years ago
  • Comments:35 (9 by maintainers)

github_iconTop GitHub Comments

61reactions
niftylettucecommented, Jun 29, 2016

Your solution does not work, this is still broken.

34reactions
TooTallNatecommented, Sep 18, 2012

Everyone, node-gyp configure must be run from the root directory of a node module. @jamcoupe Invoking it at / is likely not what you want to do.

Read more comments on GitHub >

github_iconTop Results From Across the Web

trying to 'npm install', getting node-gyp rebuild errors #809
Follow these steps to resolve the issue. 1: Make sure you have build-tools installed. ... 3: Delete package-lock.json and node modules folder and ......
Read more >
Node 10 - `node-gyp rebuild` error during npm install
Resolved the issue by updating npm to latest version & running npm rebuild.
Read more >
Npm install command failing with message "could not find ...
When I run the npm install command, npm starts downloading the dependencies. But then, suddenly, it stops with the error: npm ERR! code...
Read more >
How to Handle Node-Gyp Rebuild Failing on Mac
How to Solve the Node-gyp Rebuild Error · Restart your computer to get rid of any temporary bugs that might be affecting your...
Read more >
npm build error "node-gyp rebuild" error (#2768) - GitLab
npm build error "node-gyp rebuild" error ; gyp ERR! stack at ChildProcess.onCpExit (/home/xubuntu/.nvm/versions/node/v14.17.0/lib/node_modules/ ...
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