I think that the author and supporters may not have tested the latest version 2.1 on Windows and the problem my be due to differences between using *nx pthreads and pwinthread for multi-processing/multi-threading. Would really like to try it, but will wait until they sort this. Have logged an issue against the ghc-8.0 branch.
On Saturday, 31 December 2016 23:39:07 UTC+7, art yerkes wrote: > > I also tried it with ghc-8 and it didn't seem like it was going to work, > although I could have just not got the right steps. Decided to hold off. > Haskell changes relatively quickly compared to other languages. > > On Sat, Dec 31, 2016 at 4:14 AM, GordonBGood <[email protected] > <javascript:>> wrote: > >> On Saturday, 31 December 2016 03:25:53 UTC+7, art yerkes wrote: >>>> >>>> The promise of never needing to really get dirty and debug live Elm >>>> code is real, and it's true that nothing else quite lives up to that. >>>> >>> >>> Amen to that: the advantage of being simple and placing restrictions on >>> what one can do such that there is really only one way to do things, which >>> can be carefully tested to not cause crashes or weird behaviour... >>> >>> >>>> I wrote some notes on getting ghcjs up and running earlier. The basic >>>> trick is to ignore the initial README documentation and look on the wiki, >>>> following the directions for your specific haskell version. For 7.10: >>>> >>>> I used ghc 7.10, which doesn’t work out of the box with ghcjs. I >>>> cloned ghcjs master and used these instructions: >>>> https://github.com/ghcjs/ghcjs/wiki/GHCJS-with-GHC-7.10 from the wiki >>>> to install it properly. The quick start on the ghcjs readme doesn’t quite >>>> mention everything. In particular, you must bootstrap like: >>>> >>>> ghcjs-boot --dev --ghcjs-boot-dev-branch master --shims-dev-branch >>>> master >>>> >>> Thanks for that; there isn't a lot of help getting GHCJS to work with >> GHC 8.0.1. >> >> The encouraging news is that there is very active work going on for >> GHCJS, just not committed to the github GHCJS repository, with the latest >> (version 2.1) source available from Luite (the author of GHCJS) >> <http://luite%20%28the%20author%20of%20ghcjs/>; which to me means that >> it may reach a stable status before the others (other than Elm). >> >> As I am on Windows I used the instructions on how to set up MSYS2 as per >> the GHCJS Readme.md file to which I added $PATH addition for node (for >> later use and testing) that was installed under Windows. I then performed >> the following steps as per your suggestion, but get the following error: >> >> System\Process\Common.hs:50:31: error: >> Module `System.Win32.DebugApi' does not export `PHANDLE' >> >> GHCi\Signals.hs:9:1: error: >> Failed to load interface for `System.Posix.Signals' >> Perhaps you meant System.Posix.Internals (from base-4.9.0.0) >> Use -v to see a list of the files searched for. >> cabal.exe: Error: some packages failed to install: >> ghci-8.0.1 failed during the building phase. The exception was: >> ExitFailure 1 >> process-1.4.2.0 failed during the building phase. The exception was: >> ExitFailure 1 >> >> So can't use it. >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Elm Discuss" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/elm-discuss/Um7WIBTq9xU/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
