Build Error on Win 8.1 : 'node-gyp rebuild' #2435

Closed
adrien59cadri opened this Issue May 29, 2014 · 34 comments

Comments

Projects
None yet
@adrien59cadri

Hello

I tried to build following the build documentation for windows.
I have win 8.1, Visual 2013 Update 2, python 2.7 and python 3.3, and nodejs 0.10 installed, and github for windows.

I was using git bash (the one installed by the installer on git-scm.com)

I ran script/build, and received an error on 'node-gyp rebuild'

-> obviously I was not expecting this,
I read in the doc that node-gyp is using python 2.7, that is why I prefer to mention that I have both python 3 and 2 installed.
AND for your information runing the command "python" in my shell launches python 3 by default.

python install

adrien@WD052 /d/git_working_copies/atom (master)
$ ls /c/Python
Python27/ Python33/

adrien@WD052 /d/git_working_copies/atom (master)
$ python
Python 3.3.0 (v3.3.0:bd8afb90ebf2, Sep 29 2012, 10:55:48) [MSC v.1600 32 bit (Intel)] on win32
Type "help", "copyright", "credits" or "license" for more information.

The log is:

adrien@WD052 /d/git_working_copies/atom (master)
$ ./script/build
gypnpm ERR! runas@0.5.4 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "node" "d:\\git_working_copies\\atom\\build\\node_modules\\npm\
"install" "--quiet"
npm ERR! cwd d:\git_working_copies\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.13
npm ERR! code ELIFECYCLE

@izuzak izuzak added the build-error label May 29, 2014

@izuzak

This comment has been minimized.

Show comment
Hide comment
@izuzak

izuzak May 29, 2014

Member

@adrien59cadri Do you get different output if you make python point to Python2.7 and not Python3.3?

Member

izuzak commented May 29, 2014

@adrien59cadri Do you get different output if you make python point to Python2.7 and not Python3.3?

@adrien59cadri

This comment has been minimized.

Show comment
Hide comment
@adrien59cadri

adrien59cadri May 29, 2014

Hello

I'm sorry I did not manage to make it point to 2.7.

I tried that I forgot to mention.

Best

On 29 May 2014 16:08, Ivan Žužak notifications@github.com wrote:

@adrien59cadri https://github.com/adrien59cadri Do you get different
output if you make python point to Python2.7 and not Python3.3?


Reply to this email directly or view it on GitHub
#2435 (comment).

Hello

I'm sorry I did not manage to make it point to 2.7.

I tried that I forgot to mention.

Best

On 29 May 2014 16:08, Ivan Žužak notifications@github.com wrote:

@adrien59cadri https://github.com/adrien59cadri Do you get different
output if you make python point to Python2.7 and not Python3.3?


Reply to this email directly or view it on GitHub
#2435 (comment).

@jamlen

This comment has been minimized.

Show comment
Hide comment
@jamlen

jamlen May 30, 2014

I have exactly the same error message but for Windows 7x64. I have python v2.7.6 and no v3.3 installed. Is there a way to get more verbose output?

C:\src\atom>script\build.cmd
gypnpm ERR! runas@0.5.4 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "--userconfig=C:\\src\\atom\\.npmrc" "install" "--quiet"
npm ERR! cwd C:\src\atom\build
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! code ELIFECYCLE
npm

jamlen commented May 30, 2014

I have exactly the same error message but for Windows 7x64. I have python v2.7.6 and no v3.3 installed. Is there a way to get more verbose output?

C:\src\atom>script\build.cmd
gypnpm ERR! runas@0.5.4 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "--userconfig=C:\\src\\atom\\.npmrc" "install" "--quiet"
npm ERR! cwd C:\src\atom\build
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! code ELIFECYCLE
npm

@izuzak izuzak added the windows label Jun 2, 2014

@steveleathers

This comment has been minimized.

Show comment
Hide comment
@steveleathers

steveleathers Jun 2, 2014

I'm using Windows7x64 with Python 2.7 and all of the other correct SDKs and software installed and I'm getting the same error. I tried doing npm install node-gyp and it installed fine with no errors. However, script/build still gives me these errors.

Here's the npm-debug log:

1184 error pathwatcher@1.3.1 install: node-gyp rebuild
1184 error Exit status 1
1185 error Failed at the pathwatcher@1.3.1 install script.
1185 error This is most likely a problem with the pathwatcher package,
1185 error not with npm itself.
1185 error Tell the author that this fails on your system:
1185 error     node-gyp rebuild
1185 error You can get their info via:
1185 error     npm owner ls pathwatcher
1185 error There is likely additional logging output above.
1186 error System Windows_NT 6.1.7601
1187 error command "c:\\Program Files (x86)\\nodejs\\node.exe" "c:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
1188 error cwd c:\atom
1189 error node -v v0.10.28
1190 error npm -v 1.4.9
1191 error code ELIFECYCLE
1192 verbose exit [ 1, true ]

I'm using Windows7x64 with Python 2.7 and all of the other correct SDKs and software installed and I'm getting the same error. I tried doing npm install node-gyp and it installed fine with no errors. However, script/build still gives me these errors.

Here's the npm-debug log:

1184 error pathwatcher@1.3.1 install: node-gyp rebuild
1184 error Exit status 1
1185 error Failed at the pathwatcher@1.3.1 install script.
1185 error This is most likely a problem with the pathwatcher package,
1185 error not with npm itself.
1185 error Tell the author that this fails on your system:
1185 error     node-gyp rebuild
1185 error You can get their info via:
1185 error     npm owner ls pathwatcher
1185 error There is likely additional logging output above.
1186 error System Windows_NT 6.1.7601
1187 error command "c:\\Program Files (x86)\\nodejs\\node.exe" "c:\\Program Files (x86)\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
1188 error cwd c:\atom
1189 error node -v v0.10.28
1190 error npm -v 1.4.9
1191 error code ELIFECYCLE
1192 verbose exit [ 1, true ]
@ray73864

This comment has been minimized.

Show comment
Hide comment
@ray73864

ray73864 Jun 3, 2014

I have this exact issue on Windows 8.1 x64.

E:\Documents\GitHub\atom [master]> .\script\build
You must have Python 2.7 installed at 'C:\Python27'
E:\Documents\GitHub\atom [master]> .\script\build
gyp
gypnpm ERR! runas@0.5.4 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls runas
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin
\npm-cli.js" "--userconfig=E:\Documents\GitHub\atom.npmrc" "install" "--quiet"
npm ERR! cwd E:\Documents\GitHub\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.9
npm ERR! code ELIFECYCLE
npmE:\Documents\GitHub\atom [master]>

Running Python 2.7 in C:\Python27 and Node version 0.10.28.

ray73864 commented Jun 3, 2014

I have this exact issue on Windows 8.1 x64.

E:\Documents\GitHub\atom [master]> .\script\build
You must have Python 2.7 installed at 'C:\Python27'
E:\Documents\GitHub\atom [master]> .\script\build
gyp
gypnpm ERR! runas@0.5.4 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls runas
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin
\npm-cli.js" "--userconfig=E:\Documents\GitHub\atom.npmrc" "install" "--quiet"
npm ERR! cwd E:\Documents\GitHub\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.9
npm ERR! code ELIFECYCLE
npmE:\Documents\GitHub\atom [master]>

Running Python 2.7 in C:\Python27 and Node version 0.10.28.

@kevinsawicki

This comment has been minimized.

Show comment
Hide comment
@kevinsawicki

kevinsawicki Jun 3, 2014

Member

Can you try running npm install -g runas and see if that successfully completes?

If it doesn't, can you post the errors you see here?

Member

kevinsawicki commented Jun 3, 2014

Can you try running npm install -g runas and see if that successfully completes?

If it doesn't, can you post the errors you see here?

@ray73864

This comment has been minimized.

Show comment
Hide comment
@ray73864

ray73864 Jun 3, 2014

Comes back with:

C:\Users\ray_000\AppData\Roaming\npm\node_modules\runas>node "C:\Program Files (x86)\nodejs\node_modules\npm\bin\node-gy
p-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build t
ools for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please in
stall Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting t
he Project menu or right-click the solution, and then selecting "Upgrade Solution...". [C:\Users\ray_000\AppData\Roamin
g\npm\node_modules\runas\build\runas.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: msbuild failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\node-gyp\lib\buil
d.js:267:23)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:807:12)
gyp ERR! System Windows_NT 6.2.9200
gyp ERR! command "node" "C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "
rebuild"
gyp ERR! cwd C:\Users\ray_000\AppData\Roaming\npm\node_modules\runas
gyp ERR! node -v v0.10.28
gyp ERR! node-gyp -v v0.13.0
gyp ERR! not ok
npm ERR! runas@0.5.4 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin
\npm-cli.js" "install" "-g" "runas"
npm ERR! cwd E:\Documents\GitHub\atom
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.9
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! E:\Documents\GitHub\atom\npm-debug.log
npm ERR! not ok code 0
E:\Documents\GitHub\atom [master]>

The odd thing about that is it talks about Visual Studio 2010, but the Windows8 build instructions here on github for Atom say that on Win8 to use Visual Studio 2013 express for windows desktop which is what i have installed.

ray73864 commented Jun 3, 2014

Comes back with:

C:\Users\ray_000\AppData\Roaming\npm\node_modules\runas>node "C:\Program Files (x86)\nodejs\node_modules\npm\bin\node-gy
p-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build t
ools for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please in
stall Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting t
he Project menu or right-click the solution, and then selecting "Upgrade Solution...". [C:\Users\ray_000\AppData\Roamin
g\npm\node_modules\runas\build\runas.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: msbuild failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\node-gyp\lib\buil
d.js:267:23)
gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:98:17)
gyp ERR! stack at Process.ChildProcess._handle.onexit (child_process.js:807:12)
gyp ERR! System Windows_NT 6.2.9200
gyp ERR! command "node" "C:\Program Files (x86)\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "
rebuild"
gyp ERR! cwd C:\Users\ray_000\AppData\Roaming\npm\node_modules\runas
gyp ERR! node -v v0.10.28
gyp ERR! node-gyp -v v0.13.0
gyp ERR! not ok
npm ERR! runas@0.5.4 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "C:\Program Files (x86)\nodejs\node.exe" "C:\Program Files (x86)\nodejs\node_modules\npm\bin
\npm-cli.js" "install" "-g" "runas"
npm ERR! cwd E:\Documents\GitHub\atom
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.9
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! E:\Documents\GitHub\atom\npm-debug.log
npm ERR! not ok code 0
E:\Documents\GitHub\atom [master]>

The odd thing about that is it talks about Visual Studio 2010, but the Windows8 build instructions here on github for Atom say that on Win8 to use Visual Studio 2013 express for windows desktop which is what i have installed.

@radum

This comment has been minimized.

Show comment
Hide comment
@radum

radum Jun 5, 2014

Contributor

That is the problem actually the VS version. Every time I need to compile something I need to pass this parameter to npm --msvs_version=2012 (as I have MSVS version 2012) and then it works.

And I think this can be fixed by setting an env variable GYP_MSVS_VERSION = 2012.
Well it worked for me at least.

Contributor

radum commented Jun 5, 2014

That is the problem actually the VS version. Every time I need to compile something I need to pass this parameter to npm --msvs_version=2012 (as I have MSVS version 2012) and then it works.

And I think this can be fixed by setting an env variable GYP_MSVS_VERSION = 2012.
Well it worked for me at least.

@ray73864

This comment has been minimized.

Show comment
Hide comment
@ray73864

ray73864 Jun 5, 2014

Managed to install runas by doing 'npm install -g runas --msvs_version=2013', still can't get anywhere with 'script/build' though.

Still comes back with:

E:\Documents\GitHub\atom [master]> script/build
gypnpm ERR! runas@0.5.4 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "node" "E:\Documents\GitHub\atom\build\node_modules\npm\bin\npm-cli.js" "--userconfig=E:\Docum
ents\GitHub\atom.npmrc" "install" "--quiet"
npm ERR! cwd E:\Documents\GitHub\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.13
npm ERR! code ELIFECYCLE
gypnpm
E:\Documents\GitHub\atom [master]>

ray73864 commented Jun 5, 2014

Managed to install runas by doing 'npm install -g runas --msvs_version=2013', still can't get anywhere with 'script/build' though.

Still comes back with:

E:\Documents\GitHub\atom [master]> script/build
gypnpm ERR! runas@0.5.4 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "node" "E:\Documents\GitHub\atom\build\node_modules\npm\bin\npm-cli.js" "--userconfig=E:\Docum
ents\GitHub\atom.npmrc" "install" "--quiet"
npm ERR! cwd E:\Documents\GitHub\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.13
npm ERR! code ELIFECYCLE
gypnpm
E:\Documents\GitHub\atom [master]>

@radum

This comment has been minimized.

Show comment
Hide comment
@radum

radum Jun 5, 2014

Contributor

@ray73864 Because the --msvs_version=2013 is not passed to node-gyp when it's run by the build script. Set the GYP_MSVS_VERSION = 2013 env variable and it should work after.

Contributor

radum commented Jun 5, 2014

@ray73864 Because the --msvs_version=2013 is not passed to node-gyp when it's run by the build script. Set the GYP_MSVS_VERSION = 2013 env variable and it should work after.

@ray73864

This comment has been minimized.

Show comment
Hide comment
@ray73864

ray73864 Jun 5, 2014

Same Issue:

E:\Documents\GitHub\atom [master]> set GYP_MSVS_VERSION=2013
E:\Documents\GitHub\atom [master]> script/build
gypnpm ERR! runas@0.5.4 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "node" "E:\Documents\GitHub\atom\build\node_modules\npm\bin\npm-cli.js" "--userconfig=E:\Docum
ents\GitHub\atom.npmrc" "install" "--quiet"
npm ERR! cwd E:\Documents\GitHub\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.13
npm ERR! code ELIFECYCLE
gypnpm
E:\Documents\GitHub\atom [master]>

ray73864 commented Jun 5, 2014

Same Issue:

E:\Documents\GitHub\atom [master]> set GYP_MSVS_VERSION=2013
E:\Documents\GitHub\atom [master]> script/build
gypnpm ERR! runas@0.5.4 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "node" "E:\Documents\GitHub\atom\build\node_modules\npm\bin\npm-cli.js" "--userconfig=E:\Docum
ents\GitHub\atom.npmrc" "install" "--quiet"
npm ERR! cwd E:\Documents\GitHub\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.13
npm ERR! code ELIFECYCLE
gypnpm
E:\Documents\GitHub\atom [master]>

@radum

This comment has been minimized.

Show comment
Hide comment
@radum

radum Jun 5, 2014

Contributor

@ray73864 I don't think it works like that, you need to define it in the ENV vars, right click computer, properties, advanced system settings, env vars and add it in there.

Contributor

radum commented Jun 5, 2014

@ray73864 I don't think it works like that, you need to define it in the ENV vars, right click computer, properties, advanced system settings, env vars and add it in there.

@ray73864

This comment has been minimized.

Show comment
Hide comment
@ray73864

ray73864 Jun 5, 2014

Appears to be working fine now, did get a warning on package.json:

npm WARN package.json github-url-from-git@1.1.1 No repository field.

Other than that, it is now 'Installing modules'.

ray73864 commented Jun 5, 2014

Appears to be working fine now, did get a warning on package.json:

npm WARN package.json github-url-from-git@1.1.1 No repository field.

Other than that, it is now 'Installing modules'.

@ray73864

This comment has been minimized.

Show comment
Hide comment
@ray73864

ray73864 Jun 5, 2014

Spoke too soon, just looked back at the github for windows shell and noticed this big wall of text:

E:\Documents\GitHub\atom [master]> script/build
npm WARN package.json github-url-from-git@1.1.1 No repository field.

Installing modules failed

atom@0.101.0 preinstall E:\Documents\GitHub\atom
node -e 'process.exit(0)'

nslog@0.5.0 install E:\Documents\GitHub\atom\node_modules\nslog
node-gyp rebuild

E:\Documents\GitHub\atom\node_modules\nslog>node "E:\Documents\GitHub\atom\apm\node_modules\atom-package-manager\node_mo
dules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\nslog\build\nslog.vcxproj]

runas@0.5.4 install E:\Documents\GitHub\atom\node_modules\runas
node-gyp rebuild

E:\Documents\GitHub\atom\node_modules\runas>node "E:\Documents\GitHub\atom\apm\node_modules\atom-package-manager\node_mo
dules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\runas\build\runas.vcxproj]

scrollbar-style@0.4.0 install E:\Documents\GitHub\atom\node_modules\scrollbar-style
node-gyp rebuild

E:\Documents\GitHub\atom\node_modules\scrollbar-style>node "E:\Documents\GitHub\atom\apm\node_modules\atom-package-manag
er\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\scrollbar-style\build\scrollbar-style-observer.vcxproj]

pathwatcher@1.3.2 install E:\Documents\GitHub\atom\node_modules\pathwatcher
node-gyp rebuild

E:\Documents\GitHub\atom\node_modules\pathwatcher>node "E:\Documents\GitHub\atom\apm\node_modules\atom-package-manager\n
ode_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\pathwatcher\build\pathwatcher.vcxproj]

oniguruma@1.0.6 install E:\Documents\GitHub\atom\node_modules\oniguruma
node-gyp rebuild

E:\Documents\GitHub\atom\node_modules\oniguruma>node "E:\Documents\GitHub\atom\apm\node_modules\atom-package-manager\nod
e_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\oniguruma\build\oniguruma.vcxproj]

git-utils@1.4.0 install E:\Documents\GitHub\atom\node_modules\git-utils
node-gyp rebuild

E:\Documents\GitHub\atom\node_modules\git-utils>node "E:\Documents\GitHub\atom\apm\node_modules\atom-package-manager\nod
e_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\git-utils\build\libgit2.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\git-utils\build\zlib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\git-utils\build\http_parser.vcxproj]

npm WARN engine specificity@0.1.3: wanted: {"node":"~0.8.x"} (current: {"node":"v0.10.26","npm":"1.4.4"})
gyp
gypnpm ERR! nslog@0.5.0 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nslog@0.5.0 install script.
npm ERR! This is most likely a problem with the nslog package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls nslog
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.2.9200
npm ERR! command "E:\Documents\GitHub\atom\apm\node_modules\atom-package-manager\bin\node.exe" "E:\Documents
\GitHub\atom\apm\node_modules\atom-package-manager\node_modules\npm\bin\npm-cli.js" "--globalconfig" "E:\Docume
nts\GitHub\atom\apm\node_modules\atom-package-manager.apmrc" "--userconfig" "C:\Users\ray_000.atom.apmrc" "
install" "--target=0.11.10" "--arch=ia32" "--quiet" "--msvs_version=2010"
npm ERR! cwd E:\Documents\GitHub\atom
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.4
npm ERR! code ELIFECYCLE
npm WARN engine specificity@0.1.3: wanted: {"node":"~0.8.x"} (current: {"node":"v0.10.26","npm":"1.4.4"})
gypgypgypgypnpm
E:\Documents\GitHub\atom [master]>

ray73864 commented Jun 5, 2014

Spoke too soon, just looked back at the github for windows shell and noticed this big wall of text:

E:\Documents\GitHub\atom [master]> script/build
npm WARN package.json github-url-from-git@1.1.1 No repository field.

Installing modules failed

atom@0.101.0 preinstall E:\Documents\GitHub\atom
node -e 'process.exit(0)'

nslog@0.5.0 install E:\Documents\GitHub\atom\node_modules\nslog
node-gyp rebuild

E:\Documents\GitHub\atom\node_modules\nslog>node "E:\Documents\GitHub\atom\apm\node_modules\atom-package-manager\node_mo
dules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\nslog\build\nslog.vcxproj]

runas@0.5.4 install E:\Documents\GitHub\atom\node_modules\runas
node-gyp rebuild

E:\Documents\GitHub\atom\node_modules\runas>node "E:\Documents\GitHub\atom\apm\node_modules\atom-package-manager\node_mo
dules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\runas\build\runas.vcxproj]

scrollbar-style@0.4.0 install E:\Documents\GitHub\atom\node_modules\scrollbar-style
node-gyp rebuild

E:\Documents\GitHub\atom\node_modules\scrollbar-style>node "E:\Documents\GitHub\atom\apm\node_modules\atom-package-manag
er\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\scrollbar-style\build\scrollbar-style-observer.vcxproj]

pathwatcher@1.3.2 install E:\Documents\GitHub\atom\node_modules\pathwatcher
node-gyp rebuild

E:\Documents\GitHub\atom\node_modules\pathwatcher>node "E:\Documents\GitHub\atom\apm\node_modules\atom-package-manager\n
ode_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\pathwatcher\build\pathwatcher.vcxproj]

oniguruma@1.0.6 install E:\Documents\GitHub\atom\node_modules\oniguruma
node-gyp rebuild

E:\Documents\GitHub\atom\node_modules\oniguruma>node "E:\Documents\GitHub\atom\apm\node_modules\atom-package-manager\nod
e_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\oniguruma\build\oniguruma.vcxproj]

git-utils@1.4.0 install E:\Documents\GitHub\atom\node_modules\git-utils
node-gyp rebuild

E:\Documents\GitHub\atom\node_modules\git-utils>node "E:\Documents\GitHub\atom\apm\node_modules\atom-package-manager\nod
e_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\git-utils\build\libgit2.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\git-utils\build\zlib.vcxproj]
C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V120\Microsoft.Cpp.Platform.targets(64,5): error MSB8020: The build to
ols for Visual Studio 2010 (Platform Toolset = 'v100') cannot be found. To build using the v100 build tools, please inst
all Visual Studio 2010 build tools. Alternatively, you may upgrade to the current Visual Studio tools by selecting the
Project menu or right-click the solution, and then selecting "Upgrade Solution...". [E:\Documents\GitHub\atom\node_modul
es\git-utils\build\http_parser.vcxproj]

npm WARN engine specificity@0.1.3: wanted: {"node":"~0.8.x"} (current: {"node":"v0.10.26","npm":"1.4.4"})
gyp
gypnpm ERR! nslog@0.5.0 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the nslog@0.5.0 install script.
npm ERR! This is most likely a problem with the nslog package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls nslog
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.2.9200
npm ERR! command "E:\Documents\GitHub\atom\apm\node_modules\atom-package-manager\bin\node.exe" "E:\Documents
\GitHub\atom\apm\node_modules\atom-package-manager\node_modules\npm\bin\npm-cli.js" "--globalconfig" "E:\Docume
nts\GitHub\atom\apm\node_modules\atom-package-manager.apmrc" "--userconfig" "C:\Users\ray_000.atom.apmrc" "
install" "--target=0.11.10" "--arch=ia32" "--quiet" "--msvs_version=2010"
npm ERR! cwd E:\Documents\GitHub\atom
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.4
npm ERR! code ELIFECYCLE
npm WARN engine specificity@0.1.3: wanted: {"node":"~0.8.x"} (current: {"node":"v0.10.26","npm":"1.4.4"})
gypgypgypgypnpm
E:\Documents\GitHub\atom [master]>

@radum

This comment has been minimized.

Show comment
Hide comment
@radum

radum Jun 5, 2014

Contributor

Well the initial issue is now fixed so, don't know about this one now, never seen it :)

Contributor

radum commented Jun 5, 2014

Well the initial issue is now fixed so, don't know about this one now, never seen it :)

@kevinsawicki

This comment has been minimized.

Show comment
Hide comment
@kevinsawicki

kevinsawicki Jun 5, 2014

Member

@radum Thanks for all your help on this one, I've updated apm to use the GYP_MSVS_VERSION env var as the version passed to node-gyp when set.

Member

kevinsawicki commented Jun 5, 2014

@radum Thanks for all your help on this one, I've updated apm to use the GYP_MSVS_VERSION env var as the version passed to node-gyp when set.

@radum

This comment has been minimized.

Show comment
Hide comment
@radum

radum Jun 5, 2014

Contributor

@kevinsawicki No worries, I've been dealing with this for some time now, the problem is also with node-gyp as it was supposed to auto-detect the version but it fails to do so, I need to find some time to see where it breaks and maybe submit a fix.

Also apm has another issue on download-node.js for environments behind a corporate proxy that don't use lowercase http_proxy values but this is another issue and I think I will submit a pull request for it as it's an easy fix.

Contributor

radum commented Jun 5, 2014

@kevinsawicki No worries, I've been dealing with this for some time now, the problem is also with node-gyp as it was supposed to auto-detect the version but it fails to do so, I need to find some time to see where it breaks and maybe submit a fix.

Also apm has another issue on download-node.js for environments behind a corporate proxy that don't use lowercase http_proxy values but this is another issue and I think I will submit a pull request for it as it's an easy fix.

@kevinsawicki

This comment has been minimized.

Show comment
Hide comment
@kevinsawicki

kevinsawicki Jun 5, 2014

Member

Also apm has another issue on download-node.js for environments behind a corporate proxy that don't use lowercase http_proxy values but this is another issue and I think I will submit a pull request for it as it's an easy fix.

Yeah, this should be switched to use the proxy value in ~/.atom/.apmrc which will fall back to the right env vars since npm handles those correctly currently.

Member

kevinsawicki commented Jun 5, 2014

Also apm has another issue on download-node.js for environments behind a corporate proxy that don't use lowercase http_proxy values but this is another issue and I think I will submit a pull request for it as it's an easy fix.

Yeah, this should be switched to use the proxy value in ~/.atom/.apmrc which will fall back to the right env vars since npm handles those correctly currently.

@radum

This comment has been minimized.

Show comment
Hide comment
@radum

radum Jun 5, 2014

Contributor

Oh yeah, didn't thought of that, of course it makes more sense. You can ignore the pull request then :) you replied to fast.

Contributor

radum commented Jun 5, 2014

Oh yeah, didn't thought of that, of course it makes more sense. You can ignore the pull request then :) you replied to fast.

@kevinsawicki kevinsawicki referenced this issue in atom/apm Jun 5, 2014

Closed

request proxy options update #124

@kevinsawicki

This comment has been minimized.

Show comment
Hide comment
@kevinsawicki

kevinsawicki Jun 5, 2014

Member

@radum the proxy issue with downloading node should be fixed on master now, thanks again for reporting it.

Member

kevinsawicki commented Jun 5, 2014

@radum the proxy issue with downloading node should be fixed on master now, thanks again for reporting it.

@stevecooperorg

This comment has been minimized.

Show comment
Hide comment
@stevecooperorg

stevecooperorg Jun 5, 2014

I executed

$env:GYP_MSVS_VERSION=2013

in the git shell and then executed script/build again, and it's past the error.

I executed

$env:GYP_MSVS_VERSION=2013

in the git shell and then executed script/build again, and it's past the error.

@radum

This comment has been minimized.

Show comment
Hide comment
@radum

radum Jun 5, 2014

Contributor

@kevinsawicki cool, thanks for your help. I will test again o a fresh system but I bet it's fine.

Contributor

radum commented Jun 5, 2014

@kevinsawicki cool, thanks for your help. I will test again o a fresh system but I bet it's fine.

@tigerhawkvok

This comment has been minimized.

Show comment
Hide comment
@tigerhawkvok

tigerhawkvok Jun 6, 2014

Still getting errors:

C:\atom [master]> script/build
Node: v0.10.28
Python: v2.7.3
gypnpm ERR! runas@0.5.4 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "node" "C:\\atom\\build\\node_modules\\npm\\bin\\npm-cli.js" "--userconfig=C:\\atom\\.npmrc" "install"
"--quiet"
npm ERR! cwd C:\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.14
npm ERR! code ELIFECYCLE

Still getting errors:

C:\atom [master]> script/build
Node: v0.10.28
Python: v2.7.3
gypnpm ERR! runas@0.5.4 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "node" "C:\\atom\\build\\node_modules\\npm\\bin\\npm-cli.js" "--userconfig=C:\\atom\\.npmrc" "install"
"--quiet"
npm ERR! cwd C:\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.14
npm ERR! code ELIFECYCLE
@kevinsawicki

This comment has been minimized.

Show comment
Hide comment
@kevinsawicki

kevinsawicki Jun 6, 2014

Member

@tigerhawkvok What version of visual studio are you using? You might want to try setting the GYP_MSVS_VERSION environment variable to that version, so if you are using 2013 you would set that env var to 2013

Member

kevinsawicki commented Jun 6, 2014

@tigerhawkvok What version of visual studio are you using? You might want to try setting the GYP_MSVS_VERSION environment variable to that version, so if you are using 2013 you would set that env var to 2013

@tigerhawkvok

This comment has been minimized.

Show comment
Hide comment
@tigerhawkvok

tigerhawkvok Jun 6, 2014

Identical:

gypnpmC:\atom [master +0 ~1 -0]> set GYP_MSVS_VERSION=2013
C:\atom [master +0 ~1 -0]> script/build
Node: v0.10.28
Python: v2.7.3
gypnpm ERR! runas@0.5.4 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "node" "C:\\atom\\build\\node_modules\\npm\\bin\\npm-cli.js" "--userconfig=C:\\atom\\.npmrc" "install"
"--quiet"
npm ERR! cwd C:\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.14
npm ERR! code ELIFECYCLE

Identical:

gypnpmC:\atom [master +0 ~1 -0]> set GYP_MSVS_VERSION=2013
C:\atom [master +0 ~1 -0]> script/build
Node: v0.10.28
Python: v2.7.3
gypnpm ERR! runas@0.5.4 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "node" "C:\\atom\\build\\node_modules\\npm\\bin\\npm-cli.js" "--userconfig=C:\\atom\\.npmrc" "install"
"--quiet"
npm ERR! cwd C:\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.14
npm ERR! code ELIFECYCLE
@radum

This comment has been minimized.

Show comment
Hide comment
@radum

radum Jun 6, 2014

Contributor

@tigerhawkvok using set on windows doesn't really work as it should so try to set GYP_MSVS_VERSION as an env variable by right clicking on computer \ properties \ advanced system settings \ environment variables \ and under system variables add GYP_MSVS_VERSION with the value 2013 and then try again.

Contributor

radum commented Jun 6, 2014

@tigerhawkvok using set on windows doesn't really work as it should so try to set GYP_MSVS_VERSION as an env variable by right clicking on computer \ properties \ advanced system settings \ environment variables \ and under system variables add GYP_MSVS_VERSION with the value 2013 and then try again.

@tigerhawkvok

This comment has been minimized.

Show comment
Hide comment
@tigerhawkvok

tigerhawkvok Jun 6, 2014

Still no dice:

screenshot 2014-06-06 15 10 40

C:\Users\Philip\Dropbox\GitHub> cd c:\atom
C:\atom [master +0 ~1 -0]> script/build
Node: v0.10.28
Python: v2.7.3
gypnpm ERR! runas@0.5.4 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "node" "C:\\atom\\build\\node_modules\\npm\\bin\\npm-cli.js" "--userconfig=C:\\atom\\.npmrc" "install"
"--quiet"
npm ERR! cwd C:\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.14
npm ERR! code ELIFECYCLE

Still no dice:

screenshot 2014-06-06 15 10 40

C:\Users\Philip\Dropbox\GitHub> cd c:\atom
C:\atom [master +0 ~1 -0]> script/build
Node: v0.10.28
Python: v2.7.3
gypnpm ERR! runas@0.5.4 install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the runas@0.5.4 install script.
npm ERR! This is most likely a problem with the runas package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls runas
npm ERR! There is likely additional logging output above.

npm ERR! System Windows_NT 6.2.9200
npm ERR! command "node" "C:\\atom\\build\\node_modules\\npm\\bin\\npm-cli.js" "--userconfig=C:\\atom\\.npmrc" "install"
"--quiet"
npm ERR! cwd C:\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.14
npm ERR! code ELIFECYCLE
@tigerhawkvok

This comment has been minimized.

Show comment
Hide comment
@tigerhawkvok

tigerhawkvok Jun 7, 2014

So, it looks like though it found python27, it ran with the default "python" which I had mapped to 3.3.

It should take that into account, and manually pass the path, especially if there are multiple Pythons installed.

Or, more to the point, it should be made compatible with the major version that came out six years ago. There is no excuse anymore to have things not Python 3 compatible, especially with a NEW APPLICATION. I suppose that's a Node issue.

So, it looks like though it found python27, it ran with the default "python" which I had mapped to 3.3.

It should take that into account, and manually pass the path, especially if there are multiple Pythons installed.

Or, more to the point, it should be made compatible with the major version that came out six years ago. There is no excuse anymore to have things not Python 3 compatible, especially with a NEW APPLICATION. I suppose that's a Node issue.

@ripper2hl

This comment has been minimized.

Show comment
Hide comment
@ripper2hl

ripper2hl Jun 11, 2014

mismo problema windows 7 de 32 bits

C:\atom [master]> script/build
Node: v0.10.28
npm: v1.4.15
Python: v2.7.7
gyp
gypnpm ERR! minidump@0.7.0 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the minidump@0.7.0 install script.
npm ERR! This is most likely a problem with the minidump package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls minidump
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "node" "C:\atom\build\node_modules\npm\bin\npm-cli.js" "-
-userconfig=C:\atom.npmrc" "install" "--quiet"
npm ERR! cwd C:\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.15
npm ERR! code ELIFECYCLE

mismo problema windows 7 de 32 bits

C:\atom [master]> script/build
Node: v0.10.28
npm: v1.4.15
Python: v2.7.7
gyp
gypnpm ERR! minidump@0.7.0 install: node-gyp rebuild
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the minidump@0.7.0 install script.
npm ERR! This is most likely a problem with the minidump package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-gyp rebuild
npm ERR! You can get their info via:
npm ERR! npm owner ls minidump
npm ERR! There is likely additional logging output above.
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "node" "C:\atom\build\node_modules\npm\bin\npm-cli.js" "-
-userconfig=C:\atom.npmrc" "install" "--quiet"
npm ERR! cwd C:\atom\build
npm ERR! node -v v0.10.28
npm ERR! npm -v 1.4.15
npm ERR! code ELIFECYCLE

@hsrobmln

This comment has been minimized.

Show comment
Hide comment
@hsrobmln

hsrobmln Jun 19, 2014

@stevecooperorg Running

$env:GYP_MSVS_VERSION=2013

In Git Shell worked for me as well, getting past the node-gyp runas errors. Thanks for the suggestion

Windows 7 x64, Visual Studio 2013, Node x64 0.10.26, Python 2.7.6

@stevecooperorg Running

$env:GYP_MSVS_VERSION=2013

In Git Shell worked for me as well, getting past the node-gyp runas errors. Thanks for the suggestion

Windows 7 x64, Visual Studio 2013, Node x64 0.10.26, Python 2.7.6

@kikoucalou

This comment has been minimized.

Show comment
Hide comment
@kikoucalou

kikoucalou Jun 20, 2014

Same build error
windows 8.1, visual studio 2012, node 0.10.29, python 2.7.6

Same build error
windows 8.1, visual studio 2012, node 0.10.29, python 2.7.6

@sryze

This comment has been minimized.

Show comment
Hide comment
@sryze

sryze Aug 5, 2014

Contributor

I had the same build error but setting GYP_MSVS_VERSION to 2013 fixed this. Maybe you should add this to build instructions?

Edit: Done.

Contributor

sryze commented Aug 5, 2014

I had the same build error but setting GYP_MSVS_VERSION to 2013 fixed this. Maybe you should add this to build instructions?

Edit: Done.

benogle added a commit that referenced this issue Aug 5, 2014

@Fishbowler Fishbowler referenced this issue in EyalAr/lwip Aug 24, 2015

Closed

Build breaks on Windows 8 #173

@Xan-Kun

This comment has been minimized.

Show comment
Hide comment
@Xan-Kun

Xan-Kun Jun 2, 2017

did you install .NET 4.5.1? That solved it for me.

Xan-Kun commented Jun 2, 2017

did you install .NET 4.5.1? That solved it for me.

@lock

This comment has been minimized.

Show comment
Hide comment
@lock

lock bot Apr 1, 2018

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

lock bot commented Apr 1, 2018

This issue has been automatically locked since there has not been any recent activity after it was closed. If you can still reproduce this issue in Safe Mode then please open a new issue and fill out the entire issue template to ensure that we have enough information to address your issue. Thanks!

@atom atom locked and limited conversation to collaborators Apr 1, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.