-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
trying to 'npm install', getting node-gyp rebuild errors #809
Comments
back story: in trying to uninstall iojs and reinstall node, I entered a world of shizzao but finally got node and npm installed successfully....I tried installing node-gyp globally to no avail... |
Delete your Aside, many tools don't handle spaces in path names well ( |
sorry, when you say "$home" do you essentially mean usr/local/bin? that's what "which node-gyp" yields in term...or do you mean another location? I did change my user name by eliminating space for "_". thanks for the heads up |
I mean the HOME environment variable. :-) node-gyp normally downloads the development tarballs to |
thanks, i figured out what you meant....just tried npm install and it appears i still have rebuild issues. it looks as though my user rename didn't propogate..(?)
|
Maybe you need to log out and log in again? It's also possible that |
so redelete $HOME/.node-gyp and also .npmrc? logout and try again? I already restarted after user name change... |
Maybe just edit your .npmrc in case it contains valuable things like tokens. |
i see a .rvmrc folder in $HOME, but no .npmrc.....and how exactly would I edit it (if I could find it)? |
If you don't have a .npmrc, don't worry about it. If you do, just vim will do; it's a text file. |
I don't have one...any other ideas? I think I've tried everything on our
|
getting same problem here when trying to install |
same problem here with contextify. |
for me, the solution was fixing the space in my home folder (that was a whole other "can o' worms"). then 'npm install' worked like a charm. also, I suggest reaching out to the folks at npm if it truly is npm related. They're great! |
I also had the node-gyp rebuild error while installing utf-8-validate package through npm. Removing the space from my filepath worked for me. |
Same with botkit. howdyai/botkit#2 |
Ok, so I do not have a space in my filepath. I deleted the |
@aroc It doesn't helped for me :( |
Thanks @bnoordhuis! I had the same issue with no spaces in my file path. Deleting the original node_modules folder from my project, then deleting .node-gyp (I did not have .npmrc), restarting, and installing node in my project again with (sudo npm install) worked with no errors. Node v5.2.0 |
Yikes. It scares me to think how low-level this is that a machine restart is a potential solution... |
I had similar issues on Ubuntu 14.04, after trying everything here I finally solved it by running: sudo apt-get install build-essential As is recommended here: https://nodejs.org/en/download/package-manager/ |
I already had build-essential installed, installing libkrb5-dev did the trick for me: apt-get install libkrb5-dev |
For me, just deleting the |
Run into same error when trying to download dependencies for Node 4.2.3 |
I also deleted the |
Thanks @aroc I removed node v4.1.2 |
Thanks @JxnGraphix - your solution worked for me Node v5.7.0 |
Could be node-sass? It compiles every time I install it. |
Could be. |
Thanks, @richardlau. I will try to follow node-sass node@12.x compatibility issues. |
This has done the job |
After trying a gazillion things, only @punitnathani's solution worked for me. |
tried pretty much every suggestion and nothing works :/ anyone has a working solution without downgrading node? |
@kukoman: If it is |
@strarsis did try to downgrade node-sass, removing it, reinstalling, deleting cache, removing and reinstalling gyp... still no joy :/ |
@kukoman: No, upgrade |
In my case, |
Nothing of what suggested above worked for me, however, I solved my issue switching to a different node version (e.g. using nvm). |
same here, I had to recreate the whole project
…On Fri, 24 May 2019 at 12:18, Francesco Belvedere ***@***.***> wrote:
Nothing of what suggested above worked for me, however, I solved my issue
switching to a different node version (using nvm).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#809?email_source=notifications&email_token=AB65NBJZKWKPOTNB7ZD5CTLPW66GXA5CNFSM4BTZHD42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWE2LKA#issuecomment-495560104>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB65NBMWOUG2F55WO7XY62DPW66GXANCNFSM4BTZHD4Q>
.
|
Switching from node Thanks @belvederef 🎉 |
used nvm and downgraded to node v11.10.0, which solved my problem |
I always have a problem to rebuild a old ember app despite a yarn.lock because of this package, unacceptable... |
@woprandi: The system itself differs from the one where the bindings compilation worked, |
Only @punitnathani's solution worked for me. Downgrade from node@12.x.x to npm install -g node@11.10.0 |
For me as well @pthornhi . I had spent, probably, a few days for experiments... |
Follow these steps to resolve the issue. 1: Make sure you have build-tools installed. Source: https://codeforgeek.com/make-failed-with-exit-code-2/ |
For those who are using AMI 2, I resolve it using sudo yum groupinstall "Development Tools" Since my errors were
|
@pthornhi its worked for me. |
I am getting below error while installing btlejuice. gyp ERR! build error |
Gotta love hundreds of people checking in on a closed issue to no avail. Good maintainer ethics! |
This page is for that specific issue from 3yrs ago, which was solved. It is not catch-all place for all node-gyp failures. If you have issues with building a node module:
|
The text was updated successfully, but these errors were encountered: