Open starrychloe opened 6 years ago
I think this will be practically impossible for anyone to reproduce and diagnose unless someone builds an exact clone of every application you have installed.
yarn
calls node-sass
which calls node-gyp
which calls msbuild
which tries to call vcbuild.exe
gyp verb found first Solution file build/binding.sln
gyp verb could not find "msbuild.exe" in PATH - finding location in registry
gyp info spawn C:\Program Files (x86)\MSBuild\14.0\bin\msbuild.exe
gyp info spawn args [ 'build/binding.sln',
gyp info spawn args '/nologo',
gyp info spawn args '/p:Configuration=Release;Platform=x64' ]
Building the projects in this solution one at a time. To enable parallel build, please add the "/m" switch.
Build started 4/5/2018 5:23:29 PM.
Project "C:\Users\Chloe\workspace\catalyst_research\node_modules\node-sass\build\binding.sln" on node 1 (default targets).
ValidateSolutionConfiguration:
Building solution configuration "Release|x64".
MSBUILD : error MSB3411: Could not load the Visual C++ component "VCBuild.exe". If the component is not installed, either 1) install the Microsoft Windows SDK for Windows Server 2008 and .NET Framework 3.5, or 2) install Microsoft Visual Studio 2008. [C:\Users\Chloe\workspace\catalyst_research\node_modules\node-sass\build\binding.sln]
Done Building Project "C:\Users\Chloe\workspace\catalyst_research\node_modules\node-sass\build\binding.sln" (default targets) -- FAILED.
Build FAILED.
so this is an error being reported by msbuild.
It's not up to yarn to detect gcc
but something in the npm
install must help node-gyp
find it?
Since you can reproduce this error, it's be really helpful if you can figure out what the difference is between the npm and yarn builds. maybe the PATH is slightly different between the two builds or something.
The node-gyp
readme indicates that you either have to have the VC++ tools installed, or use windows-build-tools
Same problem.
@kuncevic's answer:
Removed the yarn.lock then after yarn install all looking good. Seems like it some package was being buggy in my case.
Do you want to request a feature or report a bug? Bug
What is the current behavior? It crashes. See log below.
If the current behavior is a bug, please provide the steps to reproduce.
yarn
What is the expected behavior? I expect it to build & install everything. I expect it to use
gcc
because it's available. I don't expect it to depend on Windows Development Kit nor Python.Please mention your node.js, yarn and operating system version. Yarn 1.5.1, Node 9.10.1, Windows 8.1, NPM 5.6.0
Additional Info
npm install
works, with warnings. I do havegcc (rubenvb-4.7.2-release) 4.7.2
in my path. Why isn't it using that? I did installvcbuildtools 2015.4
package from Chocolatey already. Also, the output on the console is too verbose and incomprehensible. https://stackoverflow.com/questions/49605198/how-do-i-make-yarn-play-nice-with-nodeLog
yarn-error.log