Closed dimsuz closed 5 years ago
Can you identify the lts version of your stack config also?
Yes, it's lts-12.4
, I believe it is taken from stack.yaml, so it shouldn't be something system-specific (if I understand correctly)...
Just in case, here's the start of my build log, right after cloning:
[dima@fprocket komposition]$ stack install
Downloaded lts-12.4 build plan.
Didn't see gi-gtk-declarative-0.4.1 in your package indices.
Updating and trying again.
Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/
Downloading timestamp
Downloading snapshot
Updating index
Updated package index downloaded
Update complete
Populated index cache.
...and then it went on with downloading/building particular dependencies.
I'm pretty sure you're missing system dependencies. I haven't built on Arch before, so the instructions are missing, but you may be able to find some guidance in the Ubuntu/Debian instructions: https://owickstrom.github.io/komposition/user-guide/installation/#debianubuntu
Oh, I didn't figure out from that log that it didn't find a system dependency, thought it's about some hackage library. I had to install Arch's extra/gobject-introspection
package and compilation continued successfully!
Great!
Probably not the best place to ask, but maybe someone knows.
After successful build of Komposition
I'm trying to poke around, and even if I do no changes, each stack rebuild unregisters many gtk related deps and rebuilds them. This takes minutes to complete and is really annoying.
Any hints why this could be happening?
$ stack build --dry-run
Would unregister locally:
gi-atk-2.0.15
gi-cairo-1.0.17
gi-gdk-3.0.16
gi-gdkpixbuf-2.0.16
gi-gio-2.0.18
gi-glib-2.0.17
gi-gobject-2.0.16
gi-gst-1.0.16
gi-gtk-3.0.24
gi-gtk-declarative-0.4.1
gi-pango-1.0.16
haskell-gi-0.21.3
komposition-0.1.0
pretty-show-1.7
Would build:
gi-atk-2.0.15: database=local, source=package index, after: gi-glib-2.0.17,gi-gobject-2.0.16,haskell-gi-0.21.3
gi-cairo-1.0.17: database=local, source=package index, after: haskell-gi-0.21.3
gi-gdk-3.0.16: database=local, source=package index, after: gi-cairo-1.0.17,gi-gdkpixbuf-2.0.16,gi-gio-2.0.18,gi-glib-2.0.17,gi-gobject-2.0.16,gi-pango-1.0.16,haskell-gi-0.21.3
gi-gdkpixbuf-2.0.16: database=local, source=package index, after: gi-gio-2.0.18,gi-glib-2.0.17,gi-gobject-2.0.16,haskell-gi-0.21.3
gi-gio-2.0.18: database=local, source=package index, after: gi-glib-2.0.17,gi-gobject-2.0.16,haskell-gi-0.21.3
gi-glib-2.0.17: database=local, source=package index, after: haskell-gi-0.21.3
gi-gobject-2.0.16: database=local, source=package index, after: gi-glib-2.0.17,haskell-gi-0.21.3
gi-gst-1.0.16: database=local, source=package index, after: gi-glib-2.0.17,gi-gobject-2.0.16,haskell-gi-0.21.3
gi-gtk-3.0.24: database=local, source=package index, after: gi-atk-2.0.15,gi-cairo-1.0.17,gi-gdk-3.0.16,gi-gdkpixbuf-2.0.16,gi-gio-2.0.18,gi-glib-2.0.17,gi-gobject-2.0.16,gi-pango-1.0.16,haskell-gi-0.21.3
gi-gtk-declarative-0.4.1: database=local, source=package index, after: gi-glib-2.0.17,gi-gobject-2.0.16,gi-gtk-3.0.24,haskell-gi-0.21.3
gi-pango-1.0.16: database=local, source=package index, after: gi-glib-2.0.17,gi-gobject-2.0.16,haskell-gi-0.21.3
haskell-gi-0.21.3: database=local, source=package index, after: pretty-show-1.7
komposition-0.1.0: database=local, source=/home/dima/projects/komposition/, after: gi-gdk-3.0.16,gi-gdkpixbuf-2.0.16,gi-glib-2.0.17,gi-gobject-2.0.16,gi-gst-1.0.16,gi-gtk-3.0.24,gi-gtk-declarative-0.4.1,gi-pango-1.0.16,haskell-gi-0.21.3
pretty-show-1.7: database=local, source=package index
If I go on and build, it will do exactly the same on the next stack build
: unregister, build again.
(stack Version 1.9.3, lts-12.4)
Or maybe you have some hint on how you do small changes + recompilation (not using stack build
perhaps?)
Describe the bug Failing to build on Arch Linux. I've cloned then done
stack install
and have this:To Reproduce Steps to reproduce the behavior:
stack install
Desktop (please complete the following information):