Re: Building GHC on Windows
Sigbjorn Finne wrote: Simon Marlow wrote: Felix Martini wrote: . All this is likely trivial to fix but at the same time these little roadblocks may also explain why few developers on Windows contribute code to GHC and Haskell. I haven't tried sync-all on Windows - can anyone help out here? It works fine, but be mindful of how 'git' handles crlf translations on Windows. Having run into this a couple of times, it certainly looks the likely cause. Felix may want to try cloning as follows: foo$ git config --global core.autocrlf false foo$ git clone http://darcs.haskell.org/ghc.git I added a note about this to the wiki, could someone who actually understands what's going on check what I've written and edit if necessary: http://hackage.haskell.org/trac/ghc/wiki/Building/GettingTheSources#GettingaGHCsourcetreeusinggit Cheers, Simon ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: Building GHC on Windows
Simon Marlow wrote: Felix Martini wrote: . All this is likely trivial to fix but at the same time these little roadblocks may also explain why few developers on Windows contribute code to GHC and Haskell. I haven't tried sync-all on Windows - can anyone help out here? It works fine, but be mindful of how 'git' handles crlf translations on Windows. Having run into this a couple of times, it certainly looks the likely cause. Felix may want to try cloning as follows: foo$ git config --global core.autocrlf false foo$ git clone http://darcs.haskell.org/ghc.git hth --sigbjorn ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: Building GHC on Windows
Felix Martini wrote: Sigbjorn Finne: It works fine, but be mindful of how 'git' handles crlf translations on Windows. Having run into this a couple of times, it certainly looks the likely cause. Felix may want to try cloning as follows: foo$ git config --global core.autocrlf false foo$ git clone http://darcs.haskell.org/ghc.git Unfortunately i cannot change the global autocrlf flag because of other projects. I edited the sync-all script to fix the problem, but is good to know that line conversions may be the cause. It would be nice if sync-all (and other scripts) were written in portable Perl. Perl runs well on Windows whereas msys is brittle. ok. Surely you could just temporarily set it as such, followed by config'ing it for that repo only rather than have it be global? I suspect tweaking that one file instead will just be the first of many such tweaks.. --sigbjorn ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Re: Building GHC on Windows
Felix Martini wrote: Simon Marlow has recently posted a patch that adds Unicode support to Handle I/O. He mentioned that it didn't work yet on Windows so i was thinking of looking at the source code to see how the new Unicode support works and perhaps try to make it work on Windows. Thanks - I've looked into it a little and it's not too hard. There's some code in the Win32 package (System.Win32.NLS) that should prove helpful, though we'll have to copy anything we need from there since base can't depend on Win32. If you manage to get your build working, keep me updated on your plans. BTW, I think the patches now have conflicts with the HEAD, but hopefully they shouldn't be too hard to fix (I'll try to get around to this soon, but I'm quite busy with other stuff at the moment). I have built GHC from source in the past on Windows and the process was cumbersome compared to building it on Linux. But i was curious to see if it has gotten easier. After reading the Wiki i decided to get the source with Git as Darcs was slow with remote downloads. Ok, that was a lot quicker than before! Let's see, i need to run sync-all to get the core libraries. I remember that i used to use darcs-all so it must be a new script. Sync-all doesn't have an extension so i probably need to run it with msys. That doesn't work, somehow my msys environment does not find git. So let's try the Git Bash environment which also uses msys (and does not have bash). Now i get a cryptic error: at ./sync-all line 99, IN line 19. It seems the script cannot determine the default remote repo. The top line shows that it is a Perl script and i don't know Perl enough to see what is wrong. I have Perl installed on this Windows pc so let's try to run the script directly. That doesn't work either: the Perl script wants to use grep and sed. All this is likely trivial to fix but at the same time these little roadblocks may also explain why few developers on Windows contribute code to GHC and Haskell. I haven't tried sync-all on Windows - can anyone help out here? Cheers, Simon ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
Building GHC on Windows
Hi all, Simon Marlow has recently posted a patch that adds Unicode support to Handle I/O. He mentioned that it didn't work yet on Windows so i was thinking of looking at the source code to see how the new Unicode support works and perhaps try to make it work on Windows. I have built GHC from source in the past on Windows and the process was cumbersome compared to building it on Linux. But i was curious to see if it has gotten easier. After reading the Wiki i decided to get the source with Git as Darcs was slow with remote downloads. Ok, that was a lot quicker than before! Let's see, i need to run sync-all to get the core libraries. I remember that i used to use darcs-all so it must be a new script. Sync-all doesn't have an extension so i probably need to run it with msys. That doesn't work, somehow my msys environment does not find git. So let's try the Git Bash environment which also uses msys (and does not have bash). Now i get a cryptic error: at ./sync-all line 99, IN line 19. It seems the script cannot determine the default remote repo. The top line shows that it is a Perl script and i don't know Perl enough to see what is wrong. I have Perl installed on this Windows pc so let's try to run the script directly. That doesn't work either: the Perl script wants to use grep and sed. All this is likely trivial to fix but at the same time these little roadblocks may also explain why few developers on Windows contribute code to GHC and Haskell. Regards, Felix ___ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
