Failure to install time package

[Claus Reinke]

|As Ganesh said, you can't rely on executing any kind of Unix command
|or any kind of shell scripts.  Nor can you assume to have any
|compiler, except ghc.
|For LLVM I simply captured the configuration using MinGW, and then
|made a custom build step that uses this information.
|
|What you really, really want for windows is a binary install.  It's a
|great shame the time package was not included in ghc 6.10.2 (since it
|was included in earlier compiler distributions).  This broke things
|for Windows users.

Simon recently collected all the pieces needed for GHC builds on
windows, so -in principle- someone could make a cabal package
that downloads and installs these pieces in their default location

http://hackage.haskell.org/trac/ghc/wiki/Building/Preparation/Windows

and then cabal could implicitly depend on that package if seeing
a package using 'build-type: configure' on Windows. That would
solve this particular issue for all cabal packages. And once GHC
becomes able to use a standard MinGW layout

http://hackage.haskell.org/trac/ghc/ticket/1502

it could also depend on such a tools package.

That is assuming the licenses are favourable for redistribution,
and the installers can be run from the commandline.

Claus

PS. of course, unnecessary dependencies aren't necessary;-)

On Mon, Apr 13, 2009 at 4:24 PM, Sittampalam, Ganesh
<ganesh.sittampalam at credit-suisse.com> wrote:
> Ashley Yakeley wrote:
>> Neil Mitchell wrote:
>>> Hi
>>>
>>> I have raised a ticket for this bug report:
>>> http://hackage.haskell.org/trac/ghc/ticket/3162
>>>
>>> I consider this issue quite serious for Windows users. Time is an
>>> important library, Windows is an important platform, GHC is an
>>> important compiler - together we end up with a fairly important
>>> problem.
>>
>> Unfortunately I don't have GHC set up for this particular platform.
>> If you or anyone with a non-Cygwin Windows GHC installation could
>> investigate this, that would be very helpful. If autotools aren't
>> appropriate for such an environment, it's going to need another build
>> system specific to that platform.
>
> Configure scripts just don't work in that environment, so there's not
> much to investigate - either an alternative build system will have to be
> found, or perhaps the output of configure can be pre-generated for this
> platform?
>
> Ganesh
>
> ===============================================================================
> Please access the attached hyperlink for an important electronic communications disclaimer:
> http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
> ===============================================================================
>
> _______________________________________________
> Libraries mailing list
> Libraries at haskell.org
> http://www.haskell.org/mailman/listinfo/libraries
>