Can I ask a silly question. I can't seem to find where stack is recommended for ghc development on the newcomers page, but why is it? I don't want to start another flame war but I can't imagine any scenario where this is useful. As far as I understand the whole benefit of stack is the curated packages.
Which are moot here since almost everything you need is in the tree aside from Happy and Alex. Seems to me this is just overcomplicating a very simple process.
Not to mention if you have to go through stack - - exec etc all for interactions with the build artifacts it would get old quickly. Also it doesn't seem reliable especially if stack is modifying the environment and or flags passed to the compiler.
Let me reiterate, I have nothing against stack, I just don't see the benefits here. Ideally you'd want your environment as simple and vanilla as possible and *totally* in your control IMHO.
What am I missing here?
Thanks,
Tamar
I use "export PATH=`stack path --bin-path`" to make the stack installed ghc available in the PATH before building ghc. And that's all.Setting the PATH works better because we do not get any extra env variables set by stack in the environment and we do not go through the stack wrapper, so it may be a little bit faster as well. The GHC_PACKAGE_PATH variable set by the stack command is especially troublesome in some cases. You can try "stack exec env" to check all vars that stack puts in your environment.-harendra_______________________________________________On 26 January 2017 at 15:52, Marius Ghita <mhitza@gmail.com> wrote:a stack-ghc-pkg script (source https://gist.github.com/mhitza/6c2b1978ef802707161041abe1d2699e )I'm using a 'stack-ghc' executable, that's only a shell wrapper to run ghc from stack (since I don't have a globally installed ghc) (source https://gist.github.com/mhitza/38fe96fb440daab28e57a50de47863d5 ), and I also have 'ghc-pkg' wrapped in the same way with- make FAILS https://gist.github.com/mhitza/95738bf49c8c87ce46c9319b4c266a2c- configure https://gist.github.com/mhitza/88c09179be3bb82024192bf6181aef13- boot https://gist.github.com/mhitza/e23df8b9ed2aac5b1b8881c70165bf3f- build.mk configuration https://gist.github.com/mhitza/2d979c64a646bdd3e097f65fd650c675Following is a list of steps that I ran and their output linked:- clone repo https://gist.github.com/mhitza/f5d4516b6c8386fe8e064f95b5ad620b
--
_______________________________________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs