gmane.comp.lang.haskell.glasgow.user

(no subject)

Hi Claus,

I was reading your instructions on the GHC wiki page,
http://hackage.haskell.org/trac/ghc/wiki/Building/Windows, and they are
wonderful - exactly what I wanted. However, they don't work. When
downloading Cygwin you are told to add haskell.org/ghc/cygwin as a path
so it can pick up the setup.ini file. However, in the latest version of
Cygwin it obvious wants signatures for all the .ini files:

---------------------------
Cygwin Setup
---------------------------
Unable to get http://www.haskell.org/ghc/cygwin/setup.ini.sig from
<http://www.haskell.org/ghc/cygwin>
---------------------------
OK   
---------------------------

Could someone please add the appropriate signature file?

Thanks

Neil

==============================================================================
Please access the attached hyperlink for an important electronic communications disclaimer: 

http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html
==============================================================================

(Continue reading)

headers

Claus Reinke | 5 Sep 18:56

Re: (no subject)

Hi Neil,

>I was reading your instructions on the GHC wiki page,
>http://hackage.haskell.org/trac/ghc/wiki/Building/Windows, and they are
>wonderful - exactly what I wanted. However, they don't work. When
>downloading Cygwin you are told to add haskell.org/ghc/cygwin as a path
>so it can pick up the setup.ini file. However, in the latest version of
>Cygwin it obvious wants signatures for all the .ini files:
>
>---------------------------
>Cygwin Setup
>---------------------------
>Unable to get http://www.haskell.org/ghc/cygwin/setup.ini.sig from
><http://www.haskell.org/ghc/cygwin>
>---------------------------
>OK   
>---------------------------
>
>Could someone please add the appropriate signature file?

Grr, not just the Haskell Cabal keeps marching on. Apparently, 
that is a change in last month's setup.exe:

    Updated: Setup.exe updated to version 2.573.2.3
    http://cygwin.com/ml/cygwin-announce/2008-08/msg00001.html

If I understand the implications correctly, one would need a
three point change to adapt properly:

- sign the setup.ini file with a key, in place

(Continue reading)

headers

Mitchell, Neil | 8 Sep 12:40

RE: Windows build

Hi Claus,

> If I understand the implications correctly, one would need a three
point change to adapt properly:
> - sign the setup.ini file with a key, in place
> - put up a public key to check against, somewhere else
> - point setup.exe to the location of the public key
> Given that all we want are the dependencies (the package is empty),
this is starting to look ridiculous (one has to put in more
administrative information than one saves from not having to specify the
dependencies by hand..).

However, the dependency package is very useful, so if its not too much
work, it would be useful.

> Please remember to update the log on the wiki page when you succeed -
the value of this log comes from being
> applied from scratch (when just updating, it is easy to miss
something).

I am keeping an up to date list of what I do and what works, so will
combine it in once I have a working build.

Thanks

Neil

==============================================================================
Please access the attached hyperlink for an important electronic communications disclaimer:

(Continue reading)