Can not build/install on Win 10

[chenyulue]

The stack version is 1.9.3. When I run stack install --flag fltkhs:bundled , I get the following info:

[1 of 2] Compiling Main ( C:\Users\chenyulue\AppData\Local\Temp\stack8512\fltkhs-0.7.0.3\Setup.hs, C:\Users\chenyulue\AppData\Local\Temp\stack8512\fltkhs-0.7.0.3.stack-work\dist\7d103d30\setup\Main.o )

C:\Users\chenyulue\AppData\Local\Temp\stack8512\fltkhs-0.7.0.3\Setup.hs:405:16: warning: [-Wdeprecations]
In the use of ‘getComponentLocalBuildInfo’
(imported from Distribution.Simple.LocalBuildInfo):
Deprecated: "This function is not well-defined, because a 'ComponentName' does not uniquely identify a 'ComponentLocalBuildInfo'. If you have a 'TargetInfo', you should use 'targetCLBI' to get the 'ComponentLocalBuildInfo'. Otherwise, use 'componentNameTargets' to get all possible 'ComponentLocalBuildInfo's. This will be removed in Cabal 2.2."
|
405 | let clbi = getComponentLocalBuildInfo lbi CLibName
| ^^^^^^^^^^^^^^^^^^^^^^^^^^

C:\Users\chenyulue\AppData\Local\Temp\stack8512\fltkhs-0.7.0.3\Setup.hs:423:35: warning: [-Wdeprecations]
In the use of ‘die’ (imported from Distribution.Simple.Utils):
Deprecated: "Messages thrown with die can't be controlled with Verbosity; use die' instead, or dieNoVerbosity if Verbosity truly is not available"
|
423 | | modeGenerateRegScript -> die "Generate Reg Script not supported"
| ^^^
[2 of 2] Compiling StackSetupShim ( C:\sr\setup-exe-src\setup-shim-Z6RU0evB.hs, C:\Users\chenyulue\AppData\Local\Temp\stack8512\fltkhs-0.7.0.3.stack-work\dist\7d103d30\setup\StackSetupShim.o )
Linking C:\Users\chenyulue\AppData\Local\Temp\stack8512\fltkhs-0.7.0.3.stack-work\dist\7d103d30\setup\setup.exe ...
Building bundled FLTK
Archive: fltk-master.zip
8d716f7254fbcf652642a47cefa7c9f58b538dbe
creating: fltk-master/
inflating: fltk-master/.clang-format
inflating: fltk-master/.gitlab-ci.yml
inflating: fltk-master/.travis.yml
……

I have no idea how to fix it. Is is realted to my stack version or cabal version? My cabal version is 2.4.1.0.

Thanks!

[deech]

I don't see an error in your output. If you're referring to the Deprecated warnings that's normal and will be fixed, just haven't gotten to it yet.