stack install issue: "Plan construction failed" #5

Activity

1. giuliohome commented on Feb 22, 2018

   

   giuliohome

   on Feb 22, 2018

   Last edited by giuliohome

   Author

   More actions

   Even if I comment out vty, just to skip the above error for a moment, the setup still fails on windows for the following

   NOTICE that
   under hmatrix 👆 there is lapack, which is written ✍️ in Fortran 90 ... and it has a dedicated website for windows
   Therefore I guess it should be possible to build the core hmatrix and hamilton libraries on windows (once these issues are fixed)

   free-4.12.4: copy/register
   vector-sized-0.6.1.0: copy/register
   Progress: 41/44
   --  While building custom Setup.hs for package hmatrix-0.18.2.0 using:
         C:\sr\setup-exe-cache\x86_64-windows\Cabal-simple_Z6RU0evB_2.0.1.0_ghc-8.2.2.exe --builddir=.stack-work\dist\5c8418a7 configure --with-ghc=C:\Users\MyHome\AppData\L
   hc.EXE --with-ghc-pkg=C:\Users\MyHome\AppData\Local\Programs\stack\x86_64-windows\ghc-8.2.2\bin\ghc-pkg.EXE --user --package-db=clear --package-db=global --package-db=C:\
   ts\a89ed542\lib --bindir=C:\sr\snapshots\a89ed542\bin --datadir=C:\sr\snapshots\a89ed542\share --libexecdir=C:\sr\snapshots\a89ed542\libexec --sysconfdir=C:\sr\snapshots\
   \hmatrix-0.18.2.0 --htmldir=C:\sr\snapshots\a89ed542\doc\hmatrix-0.18.2.0 --haddockdir=C:\sr\snapshots\a89ed542\doc\hmatrix-0.18.2.0 --dependency=array=array-0.5.2.0 --de
   nary-0.8.5.1 --dependency=bytestring=bytestring-0.10.8.2 --dependency=deepseq=deepseq-1.4.3.0 --dependency=random=random-1.1-LLUGZ7T9DqQ5vN0Jbcd0We --dependency=semigroup
   dency=split=split-0.2.3.2-7cayvoeRj5XIrIBUB58mMy --dependency=storable-complex=storable-complex-0.2.2-4WEqCO29MfMHlD0g6H5VIw --dependency=vector=vector-0.12.0.1-IUGn3M9mk
   \AppData\Local\Programs\stack\x86_64-windows\msys2-20150512\mingw64\include --extra-lib-dirs=C:\Users\MyHome\AppData\Local\Programs\stack\x86_64-windows\msys2-20150512\mi
   \Local\Programs\stack\x86_64-windows\msys2-20150512\mingw64\lib
       Process exited with code: ExitFailure 1
       Logs have been written to: C:\haskell\hamilton\.stack-work\logs\hmatrix-0.18.2.0.log
   
       Configuring hmatrix-0.18.2.0...
       Cabal-simple_Z6RU0evB_2.0.1.0_ghc-8.2.2.exe: Missing dependencies on foreign
       libraries:
       * Missing C libraries: blas, lapack
       This problem can usually be solved by installing the system packages that
       provide these libraries (you may need the "-dev" versions). If the libraries
       are already installed but in a non-standard location then you can use the
       flags --extra-include-dirs= and --extra-lib-dirs= to specify where they are.
   
   
2. mstksg commented on Feb 22, 2018

   

   mstksg

   on Feb 22, 2018

   Owner

   More actions

   Hm, I'm a bit puzzled by the original example, as the stack.yaml in HEAD specifies nightly-2018-01-21, which does include terminfo and unix. Do things still work if you modify the stack.yaml like the error message suggests?

   As for getting hmatrix to install, I haven't personally tried to get it to work on Windows Proper (it works on my windows machine now out of the box, but only because I'm using WSL presumably), but have you tried the instructions here? https://github.com/albertoruiz/hmatrix/blob/master/INSTALL.md#windows
3. giuliohome commented on Feb 22, 2018

   

   giuliohome

   on Feb 22, 2018

   Author

   More actions

   Thanks for your kind reply. Regarding the second point, hmatrix, I'm more confident it can be solved, while for the first, vty on Windows, I'm afraid the issue is not easy.
   Actually no, I haven't tried what the message suggests because I'm under the impression that it's not working on mingw...
   The official project/package says it is not supported on win...
4. mstksg commented on Feb 22, 2018

   

   mstksg

   on Feb 22, 2018

   Last edited by mstksg

   Owner

   More actions

   Ah yes, that's unfortunate :'( Some digging around shows that the story behind vty + windows is a bit complicated (jtdaugherty/vty#1).

   The library should still work without vty (it's only used for the executable); vty is sort of essential to the executable though as it essentially is just a GUI for displaying the evolution of simple systems.

   However, installing it (and running it) does work fine on my WSL installation -- is that a reasonable option for you in this situation?
5. giuliohome commented on Feb 22, 2018

   

   giuliohome

   on Feb 22, 2018

   Author

   More actions

   I've taken note of it.
   Thanks for the support.
6. giuliohome

   closed this as completedon Feb 22, 2018