npm fails on windows 7 x64 when calls to node-gyp.js rebuild

[Babay88]

system: Windows7 x64, node.js x64. python 2.7.3.
trying to install pg or sqlite3. both call node-gyp.js rebuild - and that causes an error.
sorry, I have russian windows - that causes "???"

D:\job\TimeRecordService>npm install sqlite3
 npm http GET https://registry.npmjs.org/sqlite3
 npm http 200 https://registry.npmjs.org/sqlite3
 npm http GET https://registry.npmjs.org/sqlite3/-/sqlite3-2.1.5.tgz
 npm http 200 https://registry.npmjs.org/sqlite3/-/sqlite3-2.1.5.tgz

sqlite3@2.1.5 install D:\job\TimeRecordService\node_modules\sqlite3
 node-gyp rebuild

D:\job\TimeRecordService\node_modules\sqlite3>node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin....\node_modules\node-gyp\bin\node-gyp.js" rebuild
 gyp ERR! configure error
 gyp ERR! stack Error: Command failed: CreateProcessW: ???????? ? ???????.
 gyp ERR! stack
 gyp ERR! stack at ChildProcess.exithandler (child_process.js:540:15)
 gyp ERR! stack at ChildProcess.EventEmitter.emit (events.js:91:17)
 gyp ERR! stack at maybeClose (child_process.js:638:16)
 gyp ERR! stack at Socket.ChildProcess.spawn.stdin (child_process.js:815:11)
 gyp ERR! stack at Socket.EventEmitter.emit (events.js:88:17)
 gyp ERR! stack at Socket._destroy.destroyed (net.js:357:10)
 gyp ERR! stack at process.startup.processNextTick.process._tickCallback (node.js:244:9)
 gyp ERR! System Windows_NT 6.1.7601
 gyp ERR! command "node" "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" "rebuil
 d"
 gyp ERR! cwd D:\job\TimeRecordService\node_modules\sqlite3
 gyp ERR! node -v v0.8.9
 gyp ERR! node-gyp -v v0.6.8
 gyp ERR! not ok
 npm ERR! sqlite3@2.1.5 install: node-gyp rebuild
 npm ERR! cmd "/c" "node-gyp rebuild" failed with 1

[TooTallNate]

Wow, crazy timing. I was literally just booting up my VM to report the same issue.

I should note that when invoking npm install xxx from cmd.exe, things work as expected. But when I invoke the command from a Git Bash, or Mozilla Build (which is also bash) window, then I get this error.

[piscisaureus]

odd. It works here from git-bash.

[piscisaureus]

@TooTallNate What error do you get? The ??????? doesn't really help, but I suppose that you don't have a russian windows.

[TooTallNate]

"The system cannot find the file specified."

[Babay88]

@TooTallNate, nope, I have the same error when I run "node-gyp.js rebuild" from command-line

[TooTallNate]

@Babay88 Ya, I think that happens when node-gyp tries to spawn python.exe. I think it's the same core issue though.

[TooTallNate]

@piscisaureus I think this is the same as #3968.

[Babay88]

@TooTallNate, I guess so. but I can't get any additional info on that (

[piscisaureus]

@piscisaureus I think this is the same as #3968.

@TooTallNate That'd be surprising; that issue is about being unable to spawn .bat/.cmd files, but if python.exe is on your PATH then it should just try to use that.

[Babay88]

@TooTallNate, do you think node-gyp configure runs npm ? that error is for launching bat files, not python.

D:\job\TimeRecordService>node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" configure
gyp info it worked if it ends with ok
gyp info using node-gyp@0.6.8
gyp info using node@0.8.9 | win32 | x64
gyp ERR! configure error
gyp ERR! stack Error: Command failed: CreateProcessW: ???????? ? ???????.
gyp ERR! stack
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:540:15)
gyp ERR! stack     at ChildProcess.EventEmitter.emit (events.js:91:17)
gyp ERR! stack     at maybeClose (child_process.js:638:16)
gyp ERR! stack     at Socket.ChildProcess.spawn.stdin (child_process.js:815:11)
gyp ERR! stack     at Socket.EventEmitter.emit (events.js:88:17)
gyp ERR! stack     at Socket._destroy.destroyed (net.js:357:10)
gyp ERR! stack     at process.startup.processNextTick.process._tickCallback (node.js:244:9)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "node" "C:\\Program Files\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "config
ure"
gyp ERR! cwd D:\job\TimeRecordService
gyp ERR! node -v v0.8.9
gyp ERR! node-gyp -v v0.6.8
gyp ERR! not ok

[TooTallNate]

Actually, running node-gyp rebuild manually works for me. Nix my comment
about python.exe.

On Fri, Sep 21, 2012 at 8:14 PM, Bert Belder notifications@github.amrom.workers.devwrote:

@piscisaureus https://github.com/piscisaureus I think this is the same
as #3968 #3968.

@TooTallNate https://github.com/TooTallNate That'd be surprising; that
issue is about being unable to spawn .bat/.cmd files, but if python.exe is
on your PATH then it should just try to use that.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/4047#issuecomment-8785071.

[Babay88]

??? - is a "Access is denied" error. I can't get rid of it.
I set full control to users for python27 folder and for folder where nodeJS is located. user has also full control rights for current folder too.
I ran cmd as an administrator - that didn't helped either.
and I can't find, what permission is denied.

[Babay88]

as a result if solving:
the probles was: PYTHON environment variable had value "c:\python27" - and node-gyp tryed to run a directory.
setting PYTHON="c:\python27\python.exe" ot removing it (so node-gym guessed the location) solved the error.
but... error-reporting is bad.

[muchine]

I had exactly the same problem. node-expat installation worked fine after changing PYTHON env to poin to python.exe file. However, I faced the "msbuild.exe" failure.... I have to dig around it.

[skopp]

I have this issue... tried with cmd prompt win-mingsys32 shell and then with cygwin, where I force closed the window because it seemed to be stuck.

Gosh, as I was typing, I had been trying a third time using the cmd prompt again... and this is the output:

npm install -g node-gyp
npm http GET https://registry.npmjs.org/node-gyp
npm http 200 https://registry.npmjs.org/node-gyp
npm http GET https://registry.npmjs.org/node-gyp/-/node-gyp-0.8.1.tgz
npm http 200 https://registry.npmjs.org/node-gyp/-/node-gyp-0.8.1.tgz
npm http GET https://registry.npmjs.org/which
npm http GET https://registry.npmjs.org/glob
npm http GET https://registry.npmjs.org/osenv
npm http GET https://registry.npmjs.org/request
npm http GET https://registry.npmjs.org/nopt
npm http GET https://registry.npmjs.org/minimatch
npm http GET https://registry.npmjs.org/rimraf
npm http GET https://registry.npmjs.org/fstream
npm http GET https://registry.npmjs.org/mkdirp
npm http GET https://registry.npmjs.org/graceful-fs
npm http GET https://registry.npmjs.org/semver
npm http GET https://registry.npmjs.org/npmlog
npm http GET https://registry.npmjs.org/tar
npm http 304 https://registry.npmjs.org/glob
npm http 304 https://registry.npmjs.org/nopt
npm http 200 https://registry.npmjs.org/osenv
npm http 304 https://registry.npmjs.org/minimatch
npm http 304 https://registry.npmjs.org/rimraf
npm http 200 https://registry.npmjs.org/which
npm http GET https://registry.npmjs.org/osenv/-/osenv-0.0.3.tgz
npm http GET https://registry.npmjs.org/which/-/which-1.0.5.tgz
npm http 304 https://registry.npmjs.org/request
npm http 304 https://registry.npmjs.org/mkdirp
npm http 304 https://registry.npmjs.org/graceful-fs
npm http 304 https://registry.npmjs.org/semver
npm http 304 https://registry.npmjs.org/tar
npm http 304 https://registry.npmjs.org/npmlog
npm http 200 https://registry.npmjs.org/osenv/-/osenv-0.0.3.tgz
npm http 200 https://registry.npmjs.org/fstream
npm http 200 https://registry.npmjs.org/which/-/which-1.0.5.tgz
npm http GET https://registry.npmjs.org/fstream/-/fstream-0.1.20.tgz
npm http 200 https://registry.npmjs.org/fstream/-/fstream-0.1.20.tgz
npm http GET https://registry.npmjs.org/abbrev
npm http GET https://registry.npmjs.org/ansi
npm http GET https://registry.npmjs.org/lru-cache
npm http GET https://registry.npmjs.org/sigmund
npm http GET https://registry.npmjs.org/inherits
npm http GET https://registry.npmjs.org/inherits
npm http GET https://registry.npmjs.org/inherits
npm http GET https://registry.npmjs.org/block-stream
npm http 304 https://registry.npmjs.org/ansi
npm http 304 https://registry.npmjs.org/abbrev
npm http 304 https://registry.npmjs.org/inherits
npm http 304 https://registry.npmjs.org/inherits
npm http 304 https://registry.npmjs.org/lru-cache
npm http 304 https://registry.npmjs.org/sigmund
npm http 304 https://registry.npmjs.org/inherits
npm http 304 https://registry.npmjs.org/block-stream
C:\Users\Rash\AppData\Roaming\npm\node-gyp -> C:\Users\Rash\AppData\Roaming\npm\
node_modules\node-gyp\bin\node-gyp.js
node-gyp@0.8.1  __path to ...\npm\node_modules\node-gyp
├── osenv@0.0.3
├── which@1.0.5
├── graceful-fs@1.1.14
├── semver@1.1.1
├── rimraf@2.0.3
├── mkdirp@0.3.4
├── nopt@2.0.0 (abbrev@1.0.3)
├── glob@3.1.14 (inherits@1.0.0)
├── fstream@0.1.20 (inherits@1.0.0)
├── request@2.9.203
├── npmlog@0.0.2 (ansi@0.1.2)
├── minimatch@0.2.9 (lru-cache@2.0.4, sigmund@1.0.0)
└── tar@0.1.14 (inherits@1.0.0, block-stream@0.0.6) 

As I said it just processed, so I will check it out and report soon hopefully