-
Notifications
You must be signed in to change notification settings - Fork 125
Assessing the new build route #63
Comments
The first time I tried this, it failed and told me I needed to update cabal. I manually ran Cabal:
GHC:
OS:
|
Awesome, thank you @jcollard! I added |
Fails. GHC: The Glorious Glasgow Haskell Compilation System, version 7.6.3 GHC and cabal installed with: after first failure deleted elm-platform and ran fubar script, same error. Cloning into 'elm-package'... Note: when using a sandbox, all packages are required to have consistent |
Responding to the mailing list, I got a failed build. Looks to be the same as Gary's but for completeness' sake...
The "good" news is, this looks like a cabal dependency problem, not an OS or Haskell problem. |
#65 hopefully fixes the above failing cases. |
Gonna call this experiment a failure. At this time, it seems that a single The answer is to fix |
@evancz fwiw, I've never had any issues installing via |
It is kind of logged in #60. The main problems are:
It seemed like I was getting lots of complaints about this, but now that I've gone through this mess, it seems like that's a far better set of problems to have. I think it's possible to fix both of those things, but I have not been able to figure it out. (time + unfamiliarity) If you can look, I think that'd be a far better fix than any of the things I have been trying. |
(If I copy cabal.config into the directory then nothing works because I have GHC 7.10.) For the resolver to work everything needs to be built together, though I don't think |
@jvoigtlaender just fixed the first thing you mention in #65 but it is true that different versions of GHC cannot work with the same Once that's added, maybe this route can actually work. |
Dear All Perhaps I've done something wrong but I've had no problems installing from source just now on FreeBSD. Fresh installs of GHC and cabal: $ ghci --version Then run your BuildFromSource.hs script for 0.15.1. Put the bin dir on my PATH, and: $ elm repl Thanks Ivan |
Thanks for letting us know @llaisdy! This thread actually led to a bunch of improvements from @jvoigtlaender and @rehno-lindeque getting merged into the main BuildFromSource.hs script that improved reliability quite a bit! |
In case it's relevant, after encountering issue #411 on Ubuntu 14.04, |
@jvoigtlaender here is my reply from our conversation at kevva/elm-bin#21. I followed the @alphydan 's tutorial, but first I had to update my glibc library to version >= 2.15 by following the instructions here: http://stackoverflow.com/questions/10863613/how-to-upgrade-glibc-from-version-2-13-to-2-15-on-debian. Then I got the ghc and cabal running:
I added everything to my PATH variables, got the script and ran runhaskell BuildFromSource.hs 0.15.1 . Everything looked fine, but these were the last 10 lines I got after more than one hour of compiling on my older machine:
There were few warnings about redundancy during the installation, but if I got it right everything except elm-package-0.5.1 was installed. But I can not run elm-make or elm-reactor even from the folder where they are installed:
or from .cabal-sandbox/bin directory:
I hope this helps somehow. As a reminder I have 32bit Crunchbang Waldorf linux (Debian Wheezy). |
I'm not a Linux person, but about the last points, where you are in a directory in which you have an executable like elm-make (I assume it's an executable, though an "ls -la" would be a safer way to be sure), but cannot run it: Maybe you need to call it as "./elm-make" due to some safety settings in your shell? About the actual problem with building the Elm tools: It indeed looks like something failed during the elm-package install specifically. Unfortunately the messages for that will be hidden much further above in your log. So, if you still have the Elm-Platform/0.15.1 directory lying around (with the partially successful build) could you run there just "cabal install elm-package" and post the complete output? |
Hi @jvoigtlaender, you were right, ./elm-make is the right way to run it:
Below is the dump of the "cabal install elm-package":
I would like to thank you for taking time to help me. |
Ah, sorry, I should have asked you to run "cabal install --ghc-options=-XFlexibleContexts elm-package". The build script passes this option automatically. |
Thank you @jvoigtlaender for solving my problem, it installed fine and if I run it I get:
|
Cool that it worked now. I'm a bit puzzled, because the build script should have issued an equivalent command. But unfortunately one sometimes does see such "non-deterministic" behavior with cabal builds. It could depend on some specific combination of versions of other packages being pulled in, that differed depending on whether the build script tried to build everything in one go or whether the last package was built independently. So probably we won't be able to reproduce what exactly happened here originally. But let's be content that the day you can use Elm on your machine arrived sooner rather than later. 😄 And thanks for staying through this! |
@jvoigtlaender I was playing with elm (following http://elm-by-example.org) and found out that elm-repl was not installed. I tried to install it, but I got this error:
I also tried with the --ghc-options=-XFlexibleContexts flag, but the result was the same. You can also see it was not installed by looking at my ls dumps above. Sorry, I didn't realize it that time. Elm make, reactor and package work fine. |
Not being on Linux myself, I can only guess it is related to this: elm-lang/elm-repl#46. If it is, that is if you find out that this solves your problem with elm-repl, can you please open an issue or pull request here in the elm-platform repo, so that this information is preserved for others (probably in the README somehow)? |
After building hopefully works, maybe also look out for this: elm-lang/elm-repl#57. |
I can only thank you again @jvoigtlaender. After installing libtinfo-dev, I was able to install the elm-repl. It works without --interpreter flag on Debian, I think that issue is only Ubuntu specific or was fixed already. I am just to make a pull request (I will add note to README). |
I want to track what platforms can successfully use the new build route. This is primarily meant for Linux users, but it should work for Mac users as well. Windows people, just use the installer.
Resolution: turns out that a
cabal.config
file pins downbase
and it turns out that certain compilers need certain versions of base. So for any given version of GHC, you need a differentcabal.config
file. I believe this route is doomed given how things currently work.The text was updated successfully, but these errors were encountered: