-
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
node-gyp rebuild error #2191
Comments
Python v2.7.3 -> v2.7.18 or v3.8.5 sounds like a good place to start. |
#1762 Landed in Node-gyp v5. Please try |
Try to |
Did you upgrade npm? What does log say after that? |
@cclauss, there the same log, like here: justmoon/node-bignum#121 (comment) |
Hi, also I tried installing the following configurations and gives the same error. windows 10 (os build 18363.959) - 64bit MSVS 2015 - Professional Ed windows-build-tools@5.2.2 regards. |
I believe I'm hitting the same issue.
Looking at the build error logs:
Does this indicate the version of node running is not compatible with this version of node-gyp? I could not find a compatibility table. |
It is unclear what command you typed and the full error log is missing. The label on this issue should be a clue that Please try |
@cclauss "Please try npm install -g npm or the equivalent Windows commands." worked for me! on MacOS 10.15.5
did it |
try |
|
This occurs after i installed NodeV16 with Latest Npm Version npm ERR! gyp info using node-gyp@7.1.2
npm ERR! gyp info using node@16.6.1 | win32 | ia32
npm ERR! gyp info spawn C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\MSBuild.exe
npm ERR! gyp info spawn args [
npm ERR! gyp info spawn args 'build/binding.sln',
npm ERR! gyp info spawn args '/clp:Verbosity=minimal',
npm ERR! gyp info spawn args '/nologo',
npm ERR! gyp info spawn args '/p:Configuration=Release;Platform=Win32'
npm ERR! gyp info spawn args ]
npm ERR! gyp ERR! build error
npm ERR! gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
npm ERR! gyp ERR! stack at ChildProcess.onExit (C:\Users\Priyansh Das\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\lib\build.js:194:23)
npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:394:28)
npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:290:12)
npm ERR! gyp ERR! System Windows_NT 10.0.19042
npm ERR! gyp ERR! command "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Users\\Priyansh Das\\AppData\\Roaming\\npm\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "build" "--fallback-to-build" "--module=C:\\Users\\Priyansh Das\\Desktop\\E BOT rewrite\\node_modules\\@discordjs\\opus\\prebuild\\node-v93-napi-v3-win32-ia32-unknown-unknown\\opus.node" "--module_name=opus" "--module_path=C:\\Users\\Priyansh Das\\Desktop\\E BOT rewrite\\node_modules\\@discordjs\\opus\\prebuild\\node-v93-napi-v3-win32-ia32-unknown-unknown" "--napi_version=8" "--node_abi_napi=napi" "--napi_build_version=3" "--node_napi_label=napi-v3"
npm ERR! gyp ERR! cwd C:\Users\Priyansh Das\Desktop\E BOT rewrite\node_modules\@discordjs\opus
npm ERR! gyp ERR! node -v v16.6.1
npm ERR! gyp ERR! node-gyp -v v7.1.2
npm ERR! gyp ERR! not ok
npm ERR! node-pre-gyp ERR! build error
npm ERR! node-pre-gyp ERR! stack Error: Failed to execute 'C:\Program Files (x86)\nodejs\node.exe C:\Users\Priyansh Das\AppData\Roaming\npm\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js build --fallback-to-build --module=C:\Users\Priyansh Das\Desktop\E BOT rewrite\node_modules\@discordjs\opus\prebuild\node-v93-napi-v3-win32-ia32-unknown-unknown\opus.node --module_name=opus --module_path=C:\Users\Priyansh Das\Desktop\E BOT rewrite\node_modules\@discordjs\opus\prebuild\node-v93-napi-v3-win32-ia32-unknown-unknown --napi_version=8 --node_abi_napi=napi --napi_build_version=3 --node_napi_label=napi-v3' (1)
npm ERR! node-pre-gyp ERR! stack at ChildProcess.<anonymous> (C:\Users\Priyansh Das\Desktop\E BOT rewrite\node_modules\@discordjs\node-pre-gyp\lib\util\compile.js:85:20)
npm ERR! node-pre-gyp ERR! stack at ChildProcess.emit (node:events:394:28)
npm ERR! node-pre-gyp ERR! stack at maybeClose (node:internal/child_process:1067:16)
npm ERR! node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)
npm ERR! node-pre-gyp ERR! System Windows_NT 10.0.19042
npm ERR! node-pre-gyp ERR! command "C:\\Program Files (x86)\\nodejs\\node.exe" "C:\\Users\\Priyansh Das\\Desktop\\E BOT rewrite\\node_modules\\@discordjs\\node-pre-gyp\\bin\\node-pre-gyp" "install" "--fallback-to-build"
npm ERR! node-pre-gyp ERR! cwd C:\Users\Priyansh Das\Desktop\E BOT rewrite\node_modules\@discordjs\opus
npm ERR! node-pre-gyp ERR! node -v v16.6.1
npm ERR! node-pre-gyp ERR! node-pre-gyp -v v0.4.0
npm ERR! node-pre-gyp ERR! not ok I tried
|
Same problem here :(
|
I was running an old app on Node 18 and was getting this issue. Figured I needed Node 14, so the following did it for me: nvm install 14
nvm use 14 |
Hi,
I have an application on the Windows desktop env. configured running node-gyp without errors
My desktop env is:
windows 10 (os build 18363.959) - 64bit
using Node Package Manager (nvm) v1.1.7
node v10.16.3
node-gyp v5.0.7
python v3.8.0
also in npmrc file refered to the following:
python=D:\Program Files\Python\Python27\python.exe
MSVS 2015 - Professional Ed
MSVS 2019 - Community Ed
windows-build-tools@5.2.2
But when I try to install the dependency for the same application on my laptop by running npm i it fails with the node-gyp rebuild error:
My laptop env is:
windows 10 (os build 19041.388) - 64bit
using Node Package Manager (nvm) v1.1.7
node v10.16.3
node-gyp v7.0.0
python v2.7.3
MSVS 2015 - Community Ed
MSVS 2019 - Community Ed
windows-build-tools@5.2.2
NOTE: I tried to configure with the same configurations as my desktop, also followed many references.
but the situation is the same. Could not get to fix the problem.
I also tried installing only build tools, also only installing MSVS 2015 but the result is the same.
Error is as follows:
Any recommendations would be appreciated.
Thank you very much.
The text was updated successfully, but these errors were encountered: