This is the difference between a stack with edIncludes in Installed.hs commented out, and not.
Just to show the paths that are, I assume, inserted into --extra-include-dirs and friends.
C:\projects\stack>stack install
Setting codepage to UTF-8 (65001) to ensure correct output from GHC
binary-tagged-0.1.1.0: unregistering (flags changed from ["--extra-include-dirs=C:\\Users\\clint\\AppData\\Local\\Programs\\stack\\x86_64-windows\\msys2-20150512\\mingw32\\include","--extra-include-dirs=C:\\Users\\clint\\AppData\\Local\\Programs\\stack\\x86_64-windows\\msys2-20150512\\mingw64\\include","--extra-lib-dirs=C:\\Users\\clint\\AppData\\Local\\Programs\\stack\\x86_64-windows\\msys2-20150512\\mingw32\\lib","--extra-lib-dirs=C:\\Users\\clint\\AppData\\Local\\Programs\\stack\\x86_64-windows\\msys2-20150512\\mingw64\\lib"] to ["--extra-lib-dirs=C:\\Users\\clint\\AppData\\Local\\Programs\\stack\\x86_64-windows\\msys2-20150512\\mingw32\\lib","--extra-lib-dirs=C:\\Users\\clint\\AppData\\Local\\Programs\\stack\\x86_64-windows\\msys2-20150512\\mingw64\\lib"])
stack-0.1.7.0: unregistering (missing dependencies: binary-tagged)
binary-tagged-0.1.1.0: configure
binary-tagged-0.1.1.0: build
binary-tagged-0.1.1.0: install
stack-0.1.7.0: configure
Configuring stack-0.1.7.0...
stack-0.1.7.0: build
Here's the errors from cairo built with a stock stack.exe. I included all of it just in case there's something significant.
C:\projects\cairo-0.13.1.0>..\honkj\bootstrap stack build
C:\projects\cairo-0.13.1.0>set PKG_CONFIG_PATH=C:\Users\clint\AppData\Local\Programs\stack\x86_64-windows\msys2-20150512\mingw64\lib\pkgconfig
C:\projects\cairo-0.13.1.0>set PATH=c:\Users\clint\AppData\Local\Programs\stack\x86_64-windows\msys2-20150512\mingw64\bin;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;n\;C:\Program Files\Git\cmd;C:\Users\clint\AppData\Roaming\local\bin
C:\projects\cairo-0.13.1.0>stack build
Setting codepage to UTF-8 (65001) to ensure correct output from GHC
cairo-0.13.1.0: build
Preprocessing library cairo-0.13.1.0...
In-place registering cairo-0.13.1.0...
setup.exe:
'C:\Users\clint\AppData\Local\Programs\stack\x86_64-windows\ghc-7.10.2\bin\ghc-pkg.exe'
exited with an error:
cairo-0.13.1.0: Warning: haddock-interfaces:
C:\projects\cairo-0.13.1.0\.stack-work\dist\d96ab9d9\doc\html\cairo\cairo.haddock
doesn't exist or isn't a file
cairo-0.13.1.0: Warning: haddock-html:
C:\projects\cairo-0.13.1.0\.stack-work\dist\d96ab9d9\doc\html\cairo doesn't
exist or isn't a directory
cairo-0.13.1.0: include-dirs: /mingw64/include/freetype2 is a relative path
which makes no sense (as there is nothing for it to be relative to). You can
make paths relative to the package database itself by using ${pkgroot}. (use
--force to override)
cairo-0.13.1.0: include-dirs: /mingw64/include/libpng16 is a relative path
which makes no sense (as there is nothing for it to be relative to). You can
make paths relative to the package database itself by using ${pkgroot}. (use
--force to override)
cairo-0.13.1.0: include-dirs: /mingw64/include/harfbuzz is a relative path
which makes no sense (as there is nothing for it to be relative to). You can
make paths relative to the package database itself by using ${pkgroot}. (use
--force to override)
cairo-0.13.1.0: include-dirs: /mingw64/include/glib-2.0 is a relative path
which makes no sense (as there is nothing for it to be relative to). You can
make paths relative to the package database itself by using ${pkgroot}. (use
--force to override)
cairo-0.13.1.0: include-dirs: /mingw64/lib/glib-2.0/include is a relative path
which makes no sense (as there is nothing for it to be relative to). You can
make paths relative to the package database itself by using ${pkgroot}. (use
--force to override)
-- While building package cairo-0.13.1.0 using:
C:\projects\cairo-0.13.1.0\.stack-work\dist\d96ab9d9\setup\setup --builddir=.stack-work\dist\d96ab9d9\ build lib:cairo --ghc-options " -ddump-hi -ddump-to-file"
Process exited with code: ExitFailure 1
C:\projects\cairo-0.13.1.0>