Thanks for the quick response Greg, but that did not fix the issue for me. If that were indeed the fix, then using runhaskell *BuildFromSource.hs master *would work, right? For me, it gives the same errors.
On Sunday, August 14, 2016 at 5:43:34 PM UTC-6, Gary Lockyer wrote: > > There's an issue with the version of aeson pretty > > If you edit > elm-compiler/elm-compiler.cabal > > and change the line: > aeson-pretty, > To > aeson-pretty < 0.8, > > Things should build ok. > > It looks like this has been done on master > > > https://github.com/elm-lang/elm-compiler/commit/eae9303fbed6ec929478315035fbe2e354e865e5 > > > On 15 August 2016 at 10:46, Kofi Gumbs <[email protected] <javascript:>> > wrote: > >> Hello all, >> >> I've tried to build the elm tools locally in a couple of ways, but I am >> having trouble resolving the dependency graph. I am really only interested >> in elm-make, but I've tried the recommended BuildFromSource.hs script >> <https://github.com/elm-lang/elm-platform/blob/master/installers/BuildFromSource.hs> >> as >> well. Here are the results from both approaches (cabal-install version >> 1.24.0.0, GHC version 8.0.1): >> >> *1) Just elm-make – OUTPUT >> <https://gist.github.com/hkgumbs/9c5bd3efc8cec8d51a643864621ee25a>* >> # ~/Workspaces/elm-make (git)-[0.17.1]- >> >> $ cabal sandbox delete >> $ cabal sandbox init >> $ cabal sandbox add-source ../elm-compiler # both of these are also on >> 0.17.1 >> $ cabal sandbox add-source ../elm-package >> $ cabal install -j --only-dependencies --ghc-options="-w" # these flags >> are from the BuildFromSource.hs script (I've also tried without them) >> >> >> *2) BuildFromSource.hs – OUTPUT >> <https://gist.github.com/hkgumbs/fe48186e72f1c1357441f1185543662b>* >> >> # ~/Workspaces >> >> $ rm -rf Elm-Platform BuildFromSource.hs >> $ wget https:// >> raw.githubusercontent.com/elm-lang/elm-platform/master/installers/BuildFromSource.hs >> $ runhaskell BuildFromSource.hs 0.17.1 >> >> >> >> I am not very familiar with cabal dependency management but I suspect I >> am missing some --constraint. Has anyone seen / resolved this problem >> before? I haven't had success googling this particular issue, but I have a >> nagging feeling that it's documented somewhere. >> >> -- >> 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] <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.
