Package Details: elm-platform 0.19.0-1

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

Dependencies (5)

Required by (1)

Sources (2)

Latest Comments

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

ecognito commented on 2017-10-28 04:26 (UTC)

I'm getting the same error as pfrenssen.

pfrenssen commented on 2017-10-09 11:18 (UTC)

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-1.22.5.0/build/elm-reactor/elm-reactor-tmp/StaticFiles.o ) src/backend/StaticFiles.hs:50:5: 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: $(bsToExp =<< runIO (Build.compile ("src" </> "pages" </> "Errors.elm"))) ```

Luchs commented on 2017-10-05 11:01 (UTC)

I updated the package to use stack to build, as recommended by [1]. I hope this helps! [1]: https://ruudvanasseldonk.com/2017/09/21/building-elm-with-stack

MissingNoIOI commented on 2017-10-04 14:13 (UTC)

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: hackage-security-0.5.2.2 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 (UTC)

Yes, the build commands are taken from the upstream build script at [1] which uses cabal-install. [1]: https://github.com/elm-lang/elm-platform

ptkato commented on 2017-02-16 00:17 (UTC)

Any reason to use cabal-install instead of stack?

Luchs commented on 2016-08-03 15:14 (UTC)

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: https://keybase.pub/luchs/archlinux/ 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 (UTC)

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 (UTC)

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

LeonidasXIV commented on 2016-07-12 19:31 (UTC)

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: https://github.com/elm-lang/elm-compiler/pull/1431 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`: https://gist.github.com/Leonidas-from-XIV/992c0a81627b7a146827d9543ac7d95c With this I was able to build the package.

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