Can someone explain to me why:

(1)  The GHC installation instructions state that you should install Cygwin
before installing GHC on Windows,

but

(2)  GHC seems to ship with its own versions of many of the Cygwin utilities
(including perl and the Cygwin dll)  ?

On my Windows 2000 machine, this causes problems.  When I attempt to invoke ghc,
I get the error:

$ ghc Main.hs
c:\ghc\ghc-4.08.2\bin\perl.exe: *** conflicting versions of cygwin1.dll
detected.  Use only the most recent version.

I hand-edited the first line of c:\ghc\ghc-4.08.2\bin\ghc driver script to be

#!/usr/bin/perl

instead of
#!c:/ghc/ghc-4.08.2/bin/perl

and that seemed to fix things.  But I still find this rather unnerving.

As a Cygwin user of many years, might I ask:  Why does ghc ship with its own
versions of Cygwin utilities?  I could understand this during the awkward
changeover period from Cygwin B19 to Cygwin 1.1 a year or so ago, but
(thankfully) things have stabilized considerably since then.  Nowadays, I think
shipping with your own versions of the cygwin utilities will just lead to
incompatibilities and version skew such as I observed above.  

And, I would think that it is better to require users who don't have Cygwin
installed to go through the (painless) process of installing Cygwin than it is
to fail outright for those of us who already have Cygwin.

        -antony

-- 
Antony Courtney  
Grad. Student, Dept. of Computer Science, Yale University
[EMAIL PROTECTED]          http://www.apocalypse.org/pub/u/antony

_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs

Reply via email to