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 <[email protected]> wrote: > Following is a list of steps that I ran and their output linked: > > - clone repo https://gist.github.com/mhitza/f5d4516b6c8386fe8e064f95b5ad6 > 20b > - build.mk configuration https://gist.github.com/mhitza > /2d979c64a646bdd3e097f65fd650c675 > - boot https://gist.github.com/mhitza/e23df8b9ed2aac5b1b8881c70165bf3f > - configure https://gist.github.com/mhitza/88c09179be3bb82024192bf6181ae > f13 > - make FAILS https://gist.github.com/mhitza/95738bf49c8c87ce46c9319b4c266 > a2c > > 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 > a stack-ghc-pkg script (source https://gist.github.com/mhitza > /6c2b1978ef802707161041abe1d2699e ) > > -- > Google+: https://plus.google.com/111881868112036203454 > > _______________________________________________ > ghc-devs mailing list > [email protected] > http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs > >
_______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
