Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - elm-platform

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: elm-platform 0.18.0-1

Git Clone URL: https://aur-dev.archlinux.org/elm-platform.git (read-only)
Package Base: elm-platform
Description: Bundle of all core development tools for the Elm language.
Upstream URL: http://elm-lang.org
Licenses: BSD3
Conflicts: nodejs-elm
Submitter: Luchs
Maintainer: Luchs
Last Packager: Luchs
Votes: 8
Popularity: 0.354579
First Submitted: 2015-11-20 13:48
Last Updated: 2016-11-14 15:54

Latest Comments

1 2 Next › Last »

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: 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

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:

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.

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" (https://github.com/elm-lang/elm-compiler/issues/1397).

In the end I had success building Elm with stack: https://github.com/mattjbray/arch-pkgbuilds/tree/master/elm-platform-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.

Luchs commented on 2016-06-12 20:35

There are official binaries available via npm. There is an AUR package for that as well (nodejs-elm), but it's not maintained anymore.

pepper_chico commented on 2016-06-12 20:12

It would be nice if there were a bin version. Build Haskell stuff takes too much time...

Luchs commented on 2016-06-12 14:05

Thanks, I added that.

doodad commented on 2016-06-12 12:42

I had to add

echo "allow-newer: aeson,base,HTTP,time,transformers" >> cabal.config

before 'cabal update' on the PKGBUILD as per https://github.com/elm-lang/elm-compiler/issues/1397 for me to get the build working.

Luchs commented on 2016-06-10 15:14

Did you do a clean build or did you upgrade from 0.16 in the same directory? Both the upgrade and the clean build work for me here.

`--force-reinstalls` sounds somewhat dangerous and the official build script does not include it.