===--- building phase 0
make --no-print-directory -f ghc.mk phase=0 phase_0_builds
"/mingw64/bin/ghc.exe" -O0 -H64m -Wall \
-optc-Wall -optc-Werror -optc-fno-stack-protector \
\
-hide-all-packages \
-package base -package array -package time -package containers -package bytestring -package deepseq -package process -package pretty -package directory -package Win32 \
--make utils/ghc-cabal/Main.hs -o utils/ghc-cabal/dist/build/tmp/ghc-cabal.exe \
-no-user-package-db \
-Wall -fno-warn-unused-imports -fno-warn-warnings-deprecations \
-DCABAL_VERSION= 1,25,0,0 \
-DMIN_VERSION_binary_0_8_0 \
-DBOOTSTRAPPING \
-optP-include -optPutils/ghc-cabal/cabal_macros_boot.h \
-odir bootstrapping \
-hidir bootstrapping \
-ilibraries/Cabal/Cabal \
-ilibraries/binary/src -DGENERICS \
-ilibraries/filepath \
-ilibraries/hpc \
target `1,25,0,0' is not a module name or a source file
ghc/ghc.mk:111: ghc/stage1/package-data.mk: No such file or directory
make[1]: *** [utils/ghc-cabal/ghc.mk:48: utils/ghc-cabal/dist/build/tmp/ghc-cabal.exe] Error 1
make: *** [Makefile:130: all] Error 2
Yeah, I just saw that bug report, too. Thanks.On Mon, Sep 19, 2016 at 2:37 PM, Phyx <lonetiger@gmail.com> wrote:Hi Josh,
Yes you are hitting a bug in configure that was exposed due to changes in msys.
Cherry-pick this commit to your branch https://ghc.haskell.org/trac/g
hc/ticket/12487 Tamar
On Mon, Sep 19, 2016, 12:24 Josh Berman <berman.josh@gmail.com> wrote:______________________________Hi,I was able to build the "master" branch of ghc 8.0.1 using the instructions found here:
https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/W indows When I switched to the "ghc-8.0" branch, though, I get the following error:configure: error:
You've selected:
BUILD: x86_64-w64-mingw32 (the architecture we're building on)
HOST: x86_64-unknown-mingw32 (the architecture the compiler we're building will execute on)
TARGET: x86_64-unknown-mingw32 (the architecture the compiler we're building will produce code for)
BUILD must equal HOST; that is, we do not support building GHC itself
with a cross-compiler. To cross-compile GHC itself, set TARGET: stage
1 will be a cross-compiler, and stage 2 will be the cross-compiled
GHC.Anyone know off the top of their heads what the issue is?Thanks,- Josh Berman_________________
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs