Package Details: elm-platform 0.19.0-1

Git Clone URL: (read-only, click to copy)
Package Base: elm-platform
Description: Bundle of all core development tools for the Elm language.
Upstream URL:
Keywords: elm language programming
Licenses: BSD3
Conflicts: elm-platform-bin, nodejs-elm
Submitter: Luchs
Maintainer: Luchs
Last Packager: Luchs
Votes: 18
Popularity: 0.000000
First Submitted: 2015-11-20 13:48
Last Updated: 2018-08-21 18:55

Latest Comments

« First ‹ Previous 1 2 3 4 Next › Last »

pfrenssen commented on 2017-10-09 11:18

Getting an error during the build of elm-reactor:

[4 of 8] Compiling StaticFiles ( src/backend/StaticFiles.hs, .stack-work/dist/x86_64-linux-nopie/Cabal- )

Exception when trying to run compile-time code:
elm-make: readCreateProcessWithExitCode: runInteractiveProcess: exec: does not exist (No such file or directory)
Code: (=<<)
bsToExp runIO (Build.compile ("src" </> "pages" </> "Errors.elm"))
In the splice:
=<< runIO (Build.compile ("src" </> "pages" </> "Errors.elm")))

Luchs commented on 2017-10-05 11:01

I updated the package to use stack to build, as recommended by [1]. I hope this helps!


MissingNoIOI commented on 2017-10-04 14:13

The package won't build for me, it fails with the following message:

cabal: The following packages are likely to be broken by the reinstalls:
Use --force-reinstalls if you want to install anyway.

I'm using a new, clean install of ghc and cabal

Luchs commented on 2017-02-16 09:42

Yes, the build commands are taken from the upstream build script at [1] which uses cabal-install.


ptkato commented on 2017-02-16 00:17

Any reason to use cabal-install instead of stack?

Luchs commented on 2016-08-03 15:14

I don't know, sorry.

As build issues are unfortunately really common here, I uploaded my built package
for x86_64 here, as a low-effort workaround:

I also created a repository because it seems to be really easy to do, but I did
not try it out. Packages are signed implicitly by keybase and I don't think it's
possible to verify the signatures without a keybase account, so only add this as a
repository if you're aware of the risks.

mSSM commented on 2016-08-01 21:22

Any idea what could cause the following error when building elm-reactor?

Building elm-reactor-0.17.1...
Preprocessing executable 'elm-reactor' for elm-reactor-0.17.1...
[4 of 8] Compiling StaticFiles ( src/backend/StaticFiles.hs, dist/dist-sandbox-63856d30/build/elm-reactor/elm-reactor-tmp/StaticFiles.p_o )
src/backend/StaticFiles.hs:50:3: fatal:
cannot find object file ‘dist/dist-sandbox-63856d30/build/elm-reactor/elm-reactor-tmp/StaticFiles/Build.dyn_o’
while linking an interpreted expression

Luchs commented on 2016-07-12 20:27

Thanks. I really should remember to clean the cabal cache before upgrading the package...

LeonidasXIV commented on 2016-07-12 19:31

Hi Luchs, this package FTBFS because of an API change in aeson. There is a fix available in the upstream tracker by the Elm packager of Homebrew:

I've copied the solution to this PKGBUILD. Here's a git commit to fix it, appliable with `git apply --stat elm-0.17.1-ghc-8-PKGBUILD.patch`:

With this I was able to build the package.

mattjbray commented on 2016-06-13 09:00

I ran into the "allow-newer" problem (now fixed - thanks), now I'm banging my head against:

cabal: The following packages are likely to be broken by the reinstalls:
Use --force-reinstalls if you want to install anyway.

Upstream's policy is "Elm 0.17 is just meant to be built with 7.10" (

In the end I had success building Elm with stack:

Happy to upload that to the AUR if anyone wants it, but I'm not sure what the policy is on having multiple versions of the same (built from source) package.

Equally happy (but not presuming!) for this AUR package to adopt the elm-platform-stack build method.