-
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
Build error when run from npm script #1217
Comments
@jan-j hello, |
"scripts": {
"ng": "cd node_modules/printer; node-gyp --verbose rebuild;"
},
|
So as a non-macOS-expert, what I can say is that you don't need the AFAIK
and see what it does. |
I know, I only added it to debug. It fails in both cases. Here's env output (I believe it's the same, just different format than before). |
I'm seeing the same thing while attempting to npm install something that includes
I can repro this with |
More information, I added some debug statements to node-gyp around the From a failing run:
From a successful run:
SO there is something about Any ideas? This has one of my machines completely hosed. |
Oh, and for what it's worth this repros on a homebrew installed node 8.1.0 (so no asdf in that case). |
And more info, on node 8.1.0 the failure mode is slightly different. It actually gets the |
Ok, fixed it. My problem was I had:
in my
This seems like a bug in node-gyp, yeah? |
@jan-j you also have |
@refack Yes, I had, not sure how it got there. Builds fine after removing it. Thanks. |
Happy I could be of assistance. |
Err, why is this closed? Is this not a bug? I set that variable to get rid of a nag warning from npm 5. Now I can't have it set because node gyp treats it like a path. |
@aaronjensen Sorry, I was maybe to eager to close this issue. I'm not really involved with this project, so can't say what can be done about this bug. |
Sorry for the delay. Fixed in 05d2002 . |
@bnoordhuis maybe a quick release for that fix? |
Environment:
MacOS 10.12.5
Node 7.9.0
Python 2.7.13
When doing npm install
node-gyp rebuild
command fails with the above error. But when I run the same command directly in thenode_modules/{module}
directory it works. I checked it with other native modules, so it's not related to the specific module. I also checked if python version used in the npm script run is the right one.The text was updated successfully, but these errors were encountered: