Failed to build node-gyp on Windows 7

triaged

(Satheesh Francis) #1

There are errors when I’m trying to install node packages. Could you please have look? Thanks,

Node version: v11.4.0
NPM version: 6.4.1
Windows OS: 7

This is the error:

C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js"
rebuild --release )
Building the projects in this solution one at a time. To enable parallel build,
please add the "/m" switch.
  fibers.cc
  coroutine.cc
  win_delay_load_hook.cc
p:\project\ci-com\node_modules\fibers\src\fibers.cc(464): warning C4996: 'v8::S
tring::Utf8Value::Utf8Value': was declared deprecated [P:\Project\ci-com\node_m
odules\fibers\build\fibers.vcxproj]
  c:\users\sfrancis\.node-gyp\11.4.0\include\node\v8.h(2991): note: see declara
  tion of 'v8::String::Utf8Value::Utf8Value'
p:\project\ci-com\node_modules\fibers\src\fibers.cc(686): error C2660: 'v8::Scr
ipt::Compile': function does not take 1 arguments [P:\Project\ci-com\node_modul
es\fibers\build\fibers.vcxproj]
  c:\users\sfrancis\.node-gyp\11.4.0\include\node\v8.h(1359): note: see declara
  tion of 'v8::Script::Compile' (compiling source file ..\src\fibers.cc)
p:\project\ci-com\node_modules\fibers\src\fibers.cc(701): error C2660: 'v8::Try
Catch::StackTrace': function does not take 0 arguments [P:\Project\ci-com\node_
modules\fibers\build\fibers.vcxproj]
  c:\users\sfrancis\.node-gyp\11.4.0\include\node\v8.h(8878): note: see declara
  tion of 'v8::TryCatch::StackTrace' (compiling source file ..\src\fibers.cc)
p:\project\ci-com\node_modules\fibers\src\fibers.cc(701): error C2672: 'uni::Re
set': no matching overloaded function found [P:\Project\ci-com\node_modules\fib
ers\build\fibers.vcxproj]
p:\project\ci-com\node_modules\fibers\src\fibers.cc(701): error C2780: 'void un
i::Reset(v8::Isolate *,v8::Persistent<T,v8::NonCopyablePersistentTraits<T>> &,v
8::Local<T>)': expects 3 arguments - 2 provided [P:\Project\ci-com\node_modules
\fibers\build\fibers.vcxproj]
  p:\project\ci-com\node_modules\fibers\src\fibers.cc(126): note: see declarati
  on of 'uni::Reset'
p:\project\ci-com\node_modules\fibers\src\coroutine.cc(138): warning C4552: '!'
: result of expression not used [P:\Project\ci-com\node_modules\fibers\build\fi
bers.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2017\Commu
nity\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onExit (C:\Program Files\nodejs\node_modules\
npm\node_modules\node-gyp\lib\build.js:262:23)
gyp ERR! stack     at ChildProcess.emit (events.js:189:13)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_proces
s.js:254:12)
gyp ERR! System Windows_NT 6.1.7601
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodej
s\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--rel
ease"
gyp ERR! cwd P:\Project\ci-com\node_modules\fibers
gyp ERR! node -v v11.4.0
gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
node-gyp exited with code: 1
Please make sure you are using a supported platform and node version. If you
would like to compile fibers on this machine please make sure you have setup you
r
build environment--
Windows + OS X instructions here: https://github.com/nodejs/node-gyp
Ubuntu users please run: `sudo apt-get install g++ build-essential`
Alpine users please run: `sudo apk add python make g++`
'nodejs' is not recognized as an internal or external command,
operable program or batch file.
npm WARN ciweb-automate-testing@1.0.0 No repository field.

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! fibers@2.0.2 install: `node build.js || nodejs build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the fibers@2.0.2 install script.
npm ERR! This is probably not a problem with npm. There is likely additional log
ging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\sfrancis\AppData\Roaming\npm-cache\_logs\2018-12-13T22_43_
17_382Z-debug.log

(Kat Marchán) #2

Moved to #support because this is a run-script failure, not an npm failure.