<p dir="ltr">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. </p>
<p dir="ltr">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. </p>
<p dir="ltr">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. </p>
<p dir="ltr">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. </p>
<p dir="ltr">What am I missing here? </p>
<p dir="ltr">Thanks, <br>
Tamar</p>
<br><div class="gmail_quote"><div dir="ltr">On Thu, 26 Jan 2017, 14:21 Harendra Kumar, <<a href="mailto:harendra.kumar@gmail.com">harendra.kumar@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="gmail_msg">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.<div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">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.</div></div><div dir="ltr" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg">-harendra</div></div></div><div class="gmail_extra gmail_msg"><br class="gmail_msg"><div class="gmail_quote gmail_msg">On 26 January 2017 at 15:52, Marius Ghita <span dir="ltr" class="gmail_msg"><<a href="mailto:mhitza@gmail.com" class="gmail_msg" target="_blank">mhitza@gmail.com</a>></span> wrote:<br class="gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg">Following is a list of steps that I ran and their output linked:<br class="gmail_msg"><br class="gmail_msg"></div> - clone repo <a href="https://gist.github.com/mhitza/f5d4516b6c8386fe8e064f95b5ad620b" class="gmail_msg" target="_blank">https://gist.github.com/mhitza/f5d4516b6c8386fe8e064f95b5ad620b</a><br class="gmail_msg"></div> - <a href="http://build.mk" class="gmail_msg" target="_blank">build.mk</a> configuration <a href="https://gist.github.com/mhitza/2d979c64a646bdd3e097f65fd650c675" class="gmail_msg" target="_blank">https://gist.github.com/mhitza/2d979c64a646bdd3e097f65fd650c675</a><br class="gmail_msg"></div> - boot <a href="https://gist.github.com/mhitza/e23df8b9ed2aac5b1b8881c70165bf3f" class="gmail_msg" target="_blank">https://gist.github.com/mhitza/e23df8b9ed2aac5b1b8881c70165bf3f</a><br class="gmail_msg"></div> - configure <a href="https://gist.github.com/mhitza/88c09179be3bb82024192bf6181aef13" class="gmail_msg" target="_blank">https://gist.github.com/mhitza/88c09179be3bb82024192bf6181aef13</a><br class="gmail_msg"></div> - make FAILS <a href="https://gist.github.com/mhitza/95738bf49c8c87ce46c9319b4c266a2c" class="gmail_msg" target="_blank">https://gist.github.com/mhitza/95738bf49c8c87ce46c9319b4c266a2c</a><br class="gmail_msg"><br class="gmail_msg"></div>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 <a href="https://gist.github.com/mhitza/38fe96fb440daab28e57a50de47863d5" class="gmail_msg" target="_blank">https://gist.github.com/mhitza/38fe96fb440daab28e57a50de47863d5</a> ), and I also have 'ghc-pkg' wrapped in the same way with<br class="gmail_msg"></div>a stack-ghc-pkg script (source <a href="https://gist.github.com/mhitza/6c2b1978ef802707161041abe1d2699e" class="gmail_msg" target="_blank">https://gist.github.com/mhitza/6c2b1978ef802707161041abe1d2699e</a> )<span class="m_-6694740947338633236HOEnZb gmail_msg"><font color="#888888" class="gmail_msg"><br clear="all" class="gmail_msg"><br class="gmail_msg">-- <br class="gmail_msg"><div class="m_-6694740947338633236m_-3596058171956764056gmail_signature gmail_msg">Google+: <a href="https://plus.google.com/111881868112036203454" class="gmail_msg" target="_blank">https://plus.google.com/111881868112036203454</a><br class="gmail_msg"></div>
</font></span></div>
<br class="gmail_msg">_______________________________________________<br class="gmail_msg">
ghc-devs mailing list<br class="gmail_msg">
<a href="mailto:ghc-devs@haskell.org" class="gmail_msg" target="_blank">ghc-devs@haskell.org</a><br class="gmail_msg">
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" class="gmail_msg" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br class="gmail_msg">
<br class="gmail_msg"></blockquote></div><br class="gmail_msg"></div>
_______________________________________________<br class="gmail_msg">
ghc-devs mailing list<br class="gmail_msg">
<a href="mailto:ghc-devs@haskell.org" class="gmail_msg" target="_blank">ghc-devs@haskell.org</a><br class="gmail_msg">
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" class="gmail_msg" target="_blank">http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs</a><br class="gmail_msg">
</blockquote></div>