Forwarded to the list: By the way, there are important packages such are haskell plugins, that have also this same single obstacle for workining under Windows. Many have basically the same bash script that test the type of c compiler, which fails miserably under windows: example output:
checking for C compiler default output file name... configure: error: C compiler cannot create executables See `config.log' for more details. cabal: Error: some packages failed to install: plugins-1.4.0 failed during the configure step. The exception was: exit: ExitFailure 77 Could be possible to check if this problem can be solved with cabal-install?. 2009/2/22 Duncan Coutts <duncan.cou...@worc.ox.ac.uk> > On Sun, 2009-02-22 at 18:38 +0100, Paolo Losi wrote: > > Duncan Coutts wrote: > > > > > Would it be useful to have cabal-install check a env var for its config > > > file? > > > > Definitely yes. > > This would allow dropping the dependency on bash aliasing and > > make porting to Windows fairly easy. > > Ok, I've filed a ticket so hopefully someone will pick it up. It should > be pretty easy. Just a few lines of code. > > http://hackage.haskell.org/trac/hackage/ticket/505 > > Duncan > > _______________________________________________ > Haskell-Cafe mailing list > Haskell-Cafe@haskell.org > http://www.haskell.org/mailman/listinfo/haskell-cafe >
_______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
