Skip to content
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

Rebuilds Problem (Win10 Insider Preview) #2234

Closed
mcdmaster opened this issue Oct 7, 2020 · 9 comments · May be fixed by #2259
Closed

Rebuilds Problem (Win10 Insider Preview) #2234

mcdmaster opened this issue Oct 7, 2020 · 9 comments · May be fixed by #2259
Labels

Comments

@mcdmaster
Copy link

  • Node Version: 14.13.0
  • Platform: Windows 10 Home Insider Preview 10.0.20226 N/A Build 20226
  • Compiler: 16.8.0-preview-20452-03+5dee11854
  • Module: a Nuxt.js application w/ yarn
Paste your log here, between the backticks. It can be:
  - npm --verbose output,
  - or contents of npm-debug.log,
  - or output of node-gyp rebuild --verbose.
Include the command you were trying to run.

Please see:

error C:\Users\Mac\node_modules\fibers: Command failed.
Exit code: 1
Command: node build.js || nodejs build.js
Arguments:
Directory: C:\Users\Mac\node_modules\fibers
Output:
gyp info it worked if it ends with ok
gyp info using node-gyp@7.1.0
gyp info using node@14.13.0 | win32 | x64
gyp info find Python using Python version 3.8.5 found at "C:\Python38\python.exe"
gyp ERR! find VS
gyp ERR! find VS msvs_version was set from command line or npm config
gyp ERR! find VS - looking for Visual Studio version 2019
gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
gyp ERR! find VS checking VS2019 (16.8.30524.135) found at:
gyp ERR! find VS "C:\Program Files (x86)\Microsoft Visual Studio\2019\Preview"
gyp ERR! find VS - found "Visual Studio C++ core features"
gyp ERR! find VS - found VC++ toolset: v142
gyp ERR! find VS - missing any Windows SDK
gyp ERR! find VS could not find a version of Visual Studio 2017 or newer to use
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
gyp ERR! find VS
gyp ERR! find VS valid versions for msvs_version:
gyp ERR! find VS
gyp ERR! find VS **************************************************************
gyp ERR! find VS You need to install the latest version of Visual Studio
gyp ERR! find VS including the "Desktop development with C++" workload.
gyp ERR! find VS For more information consult the documentation at:
gyp ERR! find VS https://github.com/nodejs/node-gyp#on-windows
gyp ERR! find VS **************************************************************
gyp ERR! find VS
gyp ERR! configure error
gyp ERR! stack Error: Could not find any Visual Studio installation to use
gyp ERR! stack     at VisualStudioFinder.fail (C:\Users\Mac\node_modules\node-gyp\lib\find-visualstudio.js:121:47)
gyp ERR! stack     at C:\Users\Mac\node_modules\node-gyp\lib\find-visualstudio.js:74:16
gyp ERR! stack     at VisualStudioFinder.findVisualStudio2013 (C:\Users\Mac\node_modules\node-gyp\lib\find-visualstudio.js:351:14)
gyp ERR! stack     at C:\Users\Mac\node_modules\node-gyp\lib\find-visualstudio.js:70:14
gyp ERR! stack     at C:\Users\Mac\node_modules\node-gyp\lib\find-visualstudio.js:372:16
gyp ERR! stack     at C:\Users\Mac\node_modules\node-gyp\lib\util.js:54:7
gyp ERR! stack     at C:\Users\Mac\node_modules\node-gyp\lib\util.js:33:16
gyp ERR! stack     at ChildProcess.exithandler (child_process.js:315:5)
gyp ERR! stack     at ChildProcess.emit (events.js:314:20)
gyp ERR! stack     at maybeClose (internal/child_process.js:1047:16)
gyp ERR! System Windows_NT 10.0.20226
gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Mac\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild" "--release"
gyp ERR! cwd C:\Users\Mac\node_modules\fibers
gyp ERR! node -v v14.13.0
gyp ERR! node-gyp -v v7.1.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 your
build environment--
Windows + OS X instructions here: https://github.com/nodejs/node-gyp
Ubuntu users please run: `sudo apt-get install g++ build-essential`
RHEL users please run: `yum install gcc-c++` and `yum groupinstall 'Development Tools'

Windows SDK upgrade cannot be reflected on node-gyp building platform and tries to find older SDK version

@jabbar86
Copy link

jabbar86 commented Oct 7, 2020

Try this Solution :

set node-gyp configure --msvs_version=2015(you can replace with your visual studio version)

yarn install global node-gyp

export npm_config_node_gyp=/usr/local/lib/node_modules/node-gyp/bin/node-gyp.js
(path will be different if you are using windows)

rm -rf node_modules(if already there)

yarn install

PS: Try this setup for node version < 12 i.e node 10.x.x or 11.x.x

@mcdmaster
Copy link
Author

Thanks @jabbar86 , as FYI, on my environment w/ Node 14, it was as unsuccessful as previous.
Will try older Node version(s) later

@jabbar86
Copy link

jabbar86 commented Oct 7, 2020

@mcdmaster I was facing the same issue. I downgraded to the older stable version like 10.13.0 its worked like a charm.

@mcdmaster
Copy link
Author

@jabbar86 Although I much appreciate your information indeed, I would not want to retain the "downgrade" approach. Yes, I knew that we use a magic keyword "fallback" in the case like that. I think that we would rather be in progressive fashion though.

Anyway, for my day-to-day development activities, I intend to use the "fallen back" instance. Along with that, I will look for a persistent resolution so that it can be PR'd here. Thank you anyway

@shenjackyuanjie
Copy link

I looks like got a simluare issue

❯ pnpm i
Scope: all 5 workspace projects
Lockfile is up to date, resolution step is skipped
Packages: +1676
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 0, reused 1507, downloaded 0, added 1676, done
node_modules/silk-sdk: Running install script, failed in 1.8s
node_modules/silk-sdk install$ node-gyp rebuild
│ gyp info it worked if it ends with ok
│ gyp info using node-gyp@8.4.1
│ gyp info using node@21.4.0 | win32 | x64
│ gyp info find Python using Python version 3.12.1 found at "D:\APPS\CPython\Python312\python.exe"
│ gyp ERR! find VS
│ gyp ERR! find VS msvs_version not set from command line or npm config
│ gyp ERR! find VS VCINSTALLDIR not set, not running in VS Command Prompt
│ gyp ERR! find VS checking VS2022 (17.8.34408.163) found at:
│ gyp ERR! find VS "D:\APPS\Microsoft\VisualStudio\2022-community"
│ gyp ERR! find VS - found "Visual Studio C++ core features"
│ gyp ERR! find VS - found VC++ toolset: v143
│ gyp ERR! find VS - missing any Windows SDK
│ gyp ERR! find VS could not find a version of Visual Studio 2017 or newer to use
│ gyp ERR! find VS looking for Visual Studio 2015
│ gyp ERR! find VS - not found
│ gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
│ gyp ERR! find VS
│ gyp ERR! find VS **************************************************************
│ gyp ERR! find VS You need to install the latest version of Visual Studio
│ gyp ERR! find VS including the "Desktop development with C++" workload.
│ gyp ERR! find VS For more information consult the documentation at:
│ gyp ERR! find VS https://github.com/nodejs/node-gyp#on-windows
│ gyp ERR! find VS **************************************************************
│ gyp ERR! find VS
│ gyp ERR! configure error
│ gyp ERR! stack Error: Could not find any Visual Studio installation to use
│ gyp ERR! stack     at VisualStudioFinder.fail (V:\githubs\icalingua\Icalingua-plus-plus\node_modules\node-gyp\lib\find-visualstudio.js:122:47)
│ gyp ERR! stack     at V:\githubs\icalingua\Icalingua-plus-plus\node_modules\node-gyp\lib\find-visualstudio.js:75:16
│ gyp ERR! stack     at VisualStudioFinder.findVisualStudio2013 (V:\githubs\icalingua\Icalingua-plus-plus\node_modules\node-gyp\lib\find-visualstudio.js:363:14)
│ gyp ERR! stack     at V:\githubs\icalingua\Icalingua-plus-plus\node_modules\node-gyp\lib\find-visualstudio.js:71:14
│ gyp ERR! stack     at V:\githubs\icalingua\Icalingua-plus-plus\node_modules\node-gyp\lib\find-visualstudio.js:384:16
│ gyp ERR! stack     at V:\githubs\icalingua\Icalingua-plus-plus\node_modules\node-gyp\lib\util.js:54:7
│ gyp ERR! stack     at V:\githubs\icalingua\Icalingua-plus-plus\node_modules\node-gyp\lib\util.js:33:16
│ gyp ERR! stack     at ChildProcess.exithandler (node:child_process:430:5)
│ gyp ERR! stack     at ChildProcess.emit (node:events:519:28)
│ gyp ERR! stack     at maybeClose (node:internal/child_process:1105:16)
│ gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:305:5)
│ gyp ERR! System Windows_NT 10.0.19045
│ gyp ERR! command "V:\\apps\\nodejs\\node.exe" "V:\\githubs\\icalingua\\Icalingua-plus-plus\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
│ gyp ERR! cwd V:\githubs\icalingua\Icalingua-plus-plus\node_modules\silk-sdk
│ gyp ERR! node -v v21.4.0
│ gyp ERR! node-gyp -v v8.4.1
│ gyp ERR! not ok
└─ Failed in 1.8s at V:\githubs\icalingua\Icalingua-plus-plus\node_modules\silk-sdk
 ELIFECYCLE  Command failed with exit code 1.

it happens on a pnpm i
I'm also a windows 10 insider preview

Icalingua-plus-plus [ develop][!][ v21.4.0]
❯ [System.Environment]::OSVersion

Platform ServicePack Version      VersionString
-------- ----------- -------      -------------
 Win32NT             10.0.19045.0 Microsoft Windows NT 10.0.19045.0

@shenjackyuanjie
Copy link

image

The installed windows sdk is the windows 11 latest

@shenjackyuanjie
Copy link

more info:

image

I switch My windows sdk to the windows 10 10.0.20348 and it works

@cclauss
Copy link
Contributor

cclauss commented Feb 26, 2024

gyp info using node-gyp@8.4.1

Please upgrade... https://github.com/nodejs/node-gyp/releases

@StefanStojanovic
Copy link
Contributor

This issue (especially the original one) seems no longer relevant. If there are no objections, I will close this issue next Mon-Tue. In case something similar happens again please open a new issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants