-
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
failing with "Configure error" #1040
Comments
What happens when you download the tarball manually and pass |
If I do the following...
I get this output...
The line |
Can you delete your .node-gyp directory and retry? It looks like node-gyp can't find a matching entry in SHASUMS256.txt but it seems to be using a cached, presumably corrupted version. If it had downloaded the file, there would be a 'checksum url' line in the log. |
I deleted my
|
The checksum doesn't match, compare it with https://nodejs.org/download/release/v6.9.1/SHASUMS256.txt. I'm going to guess it's something in your local network, like a virus scanner that doesn't like .lib files or some kind of corporate man-in-the-middle software. Do you have |
This is just a virtualbox image on macos, im not behind a corporate network or anything, all of this software installs fin on my mac (i also have a linux virtualbox with ubuntu and elementaryos, which these packages install fine onto). I haven't installed any additional software onto the OS, i just kept it as-is from Microsoft. I actually didn't make an .npmrc since these are all public repos, do you think that would help? |
No, a .npmrc shouldn't be necessary in that case. I don't know what is causing your issue though, only that the downloads somehow seem to end up corrupt. |
just to be sure curl wasn't downloading
The last line seems suspicious. |
It means node-gyp couldn't find an entry in SHA256SUMS.txt. However, the checksum isn't right to start with. I just downloaded https://nodejs.org/download/release/v6.9.1/win-x64/node.lib and it checksums correctly to 3951aefa4afd6fb836ab06468b1fc2a69fa75bd66ec2f5a0e08c4e32547681e3. |
If I curl
|
I suppose it's possible there is a bug in node-gyp somewhere but I can't reproduce locally and I haven't received similar bug reports so whatever it is, it must be fairly subtle and infrequent. If you have time and inclination, you could start by peppering log statements all over lib/install.js. |
Hi, |
Ok, I've found the problem for me: I've upgraded from 5.0.28 to 5.1.6, and it works fine. Downgrading to 5.0.26 would have been fine too I suppose. |
@tex0l that was it for me! im satisfied. |
Getting the same error. Using OSX and VirtualBox/docker containers.
And yes VirtualBox upgrade helped |
Same issue is happening again with Virtual Box 6.0.10 |
I'm using
node v6.9.1 (npm 3.10.8)
, on the latestIE-Preview Windows 10 VM for virtualbox
(configured by microsoft and not crippled at all). Python is also found in the path after a few tries.The problem is, I'm getting a network error when I run
node-gyp rebuild --verbose
(or just configure). This is odd because I can curl forhttps://nodejs.org/download/release/v6.9.1/node-v6.9.1-headers.tar.gz
and its a 200 (the output below also shows a 200. Here is the output...The text was updated successfully, but these errors were encountered: