This is a dumb build system problem. One way to hack around it is edit libraries/Cabal/Cabal/Cabal.cabal and remove the spaces before 1.25.0.0.
I thought I fixed this in HEAD so there may be a patch you could backport too. Edward Excerpts from Josh Berman's message of 2016-09-19 15:39:15 +0300: > Sorry to pester - now 'make' is failing: > > ===--- 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 > > > I updated my cabal to be 1.25, thinking that might be the issue, but now I > realize that was probably irrelevant. > > Any further ideas? (This time, I searched trac before emailing... but > didn't find anything). > > Thanks, > - Josh > > On Mon, Sep 19, 2016 at 2:38 PM, Josh Berman <berman.j...@gmail.com> wrote: > > > Yeah, I just saw that bug report, too. Thanks. > > > > On Mon, Sep 19, 2016 at 2:37 PM, Phyx <loneti...@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.j...@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/Windows > >>> > >>> 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 > >>> > >> > > _______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs