I'd like to discuss that in Phabricator to keep the discussion centralized. Could you add a comment?
On Fri, Aug 21, 2015 at 10:17 AM, kyra <[email protected]> wrote: > My original patch > https://ghc.haskell.org/trac/ghc/attachment/ticket/10777/cabal-rsp.patch > contains 'normslash' function. It seems, Michael have overlooked this. GNU > tools wait response files containing forward slashes in paths. > > On 21.08.2015 9:52, Tamar Christina wrote: > >> Hmm no that doesn't seem familiar to me. It looks like some Windows style >> paths are being passed around but don't know why.. >> >> Are you running the non-emulating shells? E.g. The MinGW-w64 Win64 Shell >> bat? >> ------------------------------------------------------------------------ >> From: Michael Snoyman <mailto:[email protected]> >> Sent: 8/21/2015 8:27 >> To: Tamar Christina <mailto:[email protected]> >> Cc: [email protected] <mailto:[email protected]> >> Subject: Re: Building on Windows >> >> That worked, and got me much farther. If you don't mind one more newb >> question, I'm now seeing the following. Any thoughts? >> >> ===--- building final phase >> make -r --no-print-directory -f ghc.mk <http://ghc.mk> phase=final all >> /usr/bin/install -c -m 755 utils/hp2ps/dist/build/tmp/hp2ps.exe >> inplace/bin/hp2ps.exe >> cp driver/ghc-usage.txt inplace/lib/ghc-usage.txt >> cp driver/ghci-usage.txt inplace/lib/ghci-usage.txt >> "inplace/bin/ghc-stage1.exe" -o driver/ghci/dist/build/tmp/ghci.exe >> -hisuf hi -osuf o -hcsuf hc -static -H32m -O -i -idriver/ghci/. >> -idriver/ghci/dist/build -idriver/ghci/dist/build/autogen >> -Idriver/ghci/dist/build -Idriver/ghci/dist/build/autogen >> -no-user-package-db -rtsopts -odir driver/ghci/dist/build -hidir >> driver/ghci/dist/build -stubdir driver/ghci/dist/build -static -H32m -O >> -i -idriver/ghci/. -idriver/ghci/dist/build >> -idriver/ghci/dist/build/autogen -Idriver/ghci/dist/build >> -Idriver/ghci/dist/build/autogen -no-user-package-db -rtsopts >> -no-auto-link-packages -no-hs-main driver/ghci/dist/build/ghci.o >> driver/ghci/dist/build/../utils/cwrapper.o >> driver/ghci/dist/build/../utils/getLocation.o driver/ghci/ghci.res >> Warning: -rtsopts and -with-rtsopts have no effect with -no-hs-main. >> Call hs_init_ghc() from your main() function to set these options. >> gcc.exe: error: driverghcidistbuildghci.o: No such file or directory >> gcc.exe: error: driverghcidistbuild..utilscwrapper.o: No such file or >> directory >> gcc.exe: error: driverghcidistbuild..utilsgetLocation.o: No such file or >> directory >> gcc.exe: error: driverghcighci.res: No such file or directory >> gcc.exe: error: C:msys64-2tmpghc6528_0ghc_4.o: No such file or directory >> gcc.exe: error: C:msys64-2tmpghc6528_0ghc_2.o: No such file or directory >> driver/ghci/ghc.mk:39 <http://ghc.mk:39>: recipe for target >> 'driver/ghci/dist/build/tmp/ghci.exe' failed >> make[1]: *** [driver/ghci/dist/build/tmp/ghci.exe] Error 1 >> Makefile:71: recipe for target 'all' failed >> make: *** [all] Error 2 >> >> On Fri, Aug 21, 2015 at 8:18 AM, Michael Snoyman <[email protected] >> <mailto:[email protected]>> wrote: >> >> Awesome, thanks for the quick response Tamar. Cloning now. >> >> On Fri, Aug 21, 2015 at 8:16 AM, Tamar Christina >> <[email protected] <mailto:[email protected]>> wrote: >> >> Hi Michael, >> >> Those instructions are for the GHC head. For 7.10 and earlier >> this page >> >> https://ghc.haskell.org/trac/ghc/wiki/Building/GettingTheSources/Legacy >> should have been updated but it seems it never was.. >> >> To get the tarballs on that version do >> git clone git://git.haskell.org/ghc-tarballs.git >> <http://git.haskell.org/ghc-tarballs.git> >> >> I will update the legacy page later. >> >> Regards, >> Tamar >> >> ------------------------------------------------------------------------ >> From: Michael Snoyman <mailto:[email protected]> >> Sent: 8/21/2015 7:06 >> To: [email protected] <mailto:[email protected]> >> Subject: Building on Windows >> >> I'm trying to test a patch I wrote for Windows builds[1]. I'm >> following the preparation guide[2], but my configure step >> fails[3] with config.log contents[4]. Note that I'm building >> on the ghc-7.10 branch, not master. Is it possible that this >> would contribute to the unrecognized >> --enable-tarballs-autodownload option, and/or the inability to >> compile C files? >> >> [1] https://phabricator.haskell.org/D1158, handles long linker >> command line arguments >> [2] >> >> https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Windows >> [3] http://lpaste.net/139330 >> [4] http://lpaste.net/139331 >> >> >> >> >> >> _______________________________________________ >> 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
