- cabal-devel - Haskell.org

[patch] Workaround for ar and ld for Windows cmdline length restriction
by Esa Ilari Vuokko 10 May '06

10 May '06

Hi I have prepared a patch that works around Windows 32k command line length restriction when invoking ar and ld, this makes using ghc's split-objs possible in practice. Tue May 9 04:15:32 FLE Daylight Time 2006 Esa Ilari Vuokko <ei(a)vuokko.info> * Workaround for ar and ld for Windows cmdline length restriction There is no guarantee that algorithm works, ideally I should cut the lines at 32k, but instead I just call ar/ld for each one hundred files. Ld's case is a bit more complicated, with temp files. Algorithms aren't perfect, but I think they fit practically all packages out there (who has path to object file longer than 320+ characters, and hundred more?) Better solution would be to use ar's and ld's @file-functionality, but this isn't available in mingw's stable (or whatever) binutils yet, and of course builds for 6.4.x series will never have them, so it'd need ar/ld version checking which isn't totally trivial to add. Best regards, --Esa PS. Please CC me on replies as I am not subscribed. PSS. It seems to me that indentation in source has both tabs and spaces. That feels risky.

2 1

Re: Cabal-Install doesn't work well on Windows.
by shelarcy 10 May '06

10 May '06

Hello. On Thu, 04 May 2006 09:31:35 +0900, Isaac Jones <ijones(a)syntaxpolice.org> wrote: > I'm sorry I didn't reply earlier. We're scrapping that version of > cabal-install and replacing it with a better version that can download > packages from the internet. I'd certainly be happy to hear any > reports of how this works on windows. I don't know if it works at > all, and so any help would be great. Windows (mingw) version of GHC has no System.Posix.Signals functions and Types. System.Posix.Signals module exist, but no definition now. Because Windows' native posix support is very very poor, so signal support is also poor. Cause of these reason. I can't build cabal-install on Windows Enviorment. runhaskell Setup.lhs build notice these errors; ----- ../Network/Hackage/CabalInstall/Install.hs:107:39 Not in scope: `installHandler' ../Network/Hackage/CabalInstall/Install.hs:107:54 Not in scope: `keyboardSignal' ../Network/Hackage/CabalInstall/Install.hs:107:70 Not in scope: data constructor `Catch' ../Network/Hackage/CabalInstall/Install.hs:109:25 Not in scope: `installHandler' ../Network/Hackage/CabalInstall/Install.hs:109:40 Not in scope: `keyboardSignal' ---- Does anyone have plan to support cabakl-install on Windows? Or does anyone know that how to solove these problems? -- shelarcy <shelarcy capella.freemail.ne.jp> http://page.freett.com/shelarcy/

1 0

darcs patch: Change calls to 'make' into '$(MAKE)'
by Duncan Coutts 02 May '06

02 May '06

Tue May 2 18:46:30 BST 2006 Duncan Coutts <duncan.coutts(a)worc.ox.ac.uk> * Change calls to 'make' into '$(MAKE)' This is the portable thing to do and fixes things on FreeBSD where make/=gmake

1 0