Cannot build GHC using the Newcomers guide

Harendra Kumar harendra.kumar at
Thu Jan 26 14:21:17 UTC 2017

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.


On 26 January 2017 at 15:52, Marius Ghita <mhitza at> wrote:

> Following is a list of steps that I ran and their output linked:
>  - clone repo
> 20b
>  - configuration
> /2d979c64a646bdd3e097f65fd650c675
>  - boot
>  - configure
> f13
>  - make FAILS
> 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
> ), and I
> also have 'ghc-pkg' wrapped in the same way with
> a stack-ghc-pkg script (source
> /6c2b1978ef802707161041abe1d2699e )
> --
> Google+:
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the ghc-devs mailing list