I would personally avoid the use of mintty because of how it implements pty
OK thanks. If I remember correctly you have a setup where you use bash directly in emacs. Correct In which case you just need To set the environment variables and add /mingw64/bin to your path. But set which envt variables to what, precisely? As I say in another email, c:/mingw64 doesn’t exist. c:/msys64 does, and c:/msys64/mingw64. Very confusing! Thanks Simon From: [email protected] <[email protected]> Sent: 26 March 2018 11:09 To: Simon Peyton Jones <[email protected]>; Shao, Cheng <[email protected]>; [email protected] Subject: RE: Windows “C:\msys64\msys2_shell.cmd -mingw64 -mintty” Won’t work for you as it spawns a new process using mintty as your terminal emulator. If I remember correctly you have a setup where you use bash directly in emacs. In which case you just need To set the environment variables and add /mingw64/bin to your path. I would personally avoid the use of mintty because of how it implements pty. Lots of interactive programs don’t work Correctly under it, including ghci where we need specific hacks to work around some of it’s issues https://github.com/mintty/mintty/issues/56. From: Simon Peyton Jones via ghc-devs<mailto:[email protected]> Sent: Monday, March 26, 2018 11:03 To: Shao, Cheng<mailto:[email protected]>; [email protected]<mailto:[email protected]> Subject: RE: Windows If the build environment is managed by an MSYS2 installation, then the MinGW64 shell startup script automatically sets up "MSYSTEM" for you. It can be launched like "C:\msys64\msys2_shell.cmd -mingw64 -mintty". Well I just followed the Method A instructions at https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Windows Are you saying that I should run “C:\msys64\msys2_shell.cmd -mingw64 -mintty" just once, after installing? Or repeatedly? Or that I should somehow us it as my main shell? And what does that commend actually do? Sorry to be dense Simon From: ghc-devs <[email protected]<mailto:[email protected]>> On Behalf Of Shao, Cheng Sent: 26 March 2018 10:59 To: [email protected]<mailto:[email protected]> Subject: Re: Windows Hi Simon, If the build environment is managed by an MSYS2 installation, then the MinGW64 shell startup script automatically sets up "MSYSTEM" for you. It can be launched like "C:\msys64\msys2_shell.cmd -mingw64 -mintty". On Mon, Mar 26, 2018 at 5:46 PM, Simon Peyton Jones via ghc-devs <[email protected]<mailto:[email protected]>> wrote: Making it part of the error message would be v helpful. I have added a section to "Troubleshooting" on https://ghc.haskell.org/trac/ghc/wiki/Building/Preparation/Windows But it should really be part of the instructions higher up to sa export MSYSTEM=MINGW64 Might someone do that? I wasn't quite sure where Simon | -----Original Message----- | From: ghc-devs <[email protected]<mailto:[email protected]>> On Behalf Of Ben Gamari | Sent: 24 March 2018 16:42 | To: Gabor Greif <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> | Cc: [email protected]<mailto:[email protected]> | Subject: Re: Windows | | Gabor Greif <[email protected]<mailto:[email protected]>> writes: | | > Just an idea... | > | > could this hint be part of the `configure` error message? | > | Indeed. See D4526. | | Cheers, | | - Ben _______________________________________________ ghc-devs mailing list [email protected]<mailto:[email protected]> http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fmail.haskell.org%2Fcgi-bin%2Fmailman%2Flistinfo%2Fghc-devs&data=02%7C01%7Csimonpj%40microsoft.com%7Ceee757b199a44030ad4308d59301a528%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636576557630037503&sdata=LhSYEM%2Bt6PcvOkJulJDFO0Ox4F8jlYcp0KozK8KDciY%3D&reserved=0>
_______________________________________________ ghc-devs mailing list [email protected] http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs
