ghc/cygwin filename resolution issue.

Hal Daume III hdaume@ISI.EDU
Tue, 28 Jan 2003 11:37:56 -0800 (PST)

It's been a while since I've installed GHC on Windows, but I believe back
when I did it (5.00 or something), you needed to have cygwin installed in
c:\, not c:\cygwin, despite cygwin's protests.  I don't know if this has
changed, though.

 - Hal

Hal Daume III

 "Computer science is no more about computers    |
  than astronomy is about telescopes." -Dijkstra |

On Tue, 28 Jan 2003, Alex Ferguson wrote:

> Using ghc-5.04.2 under cygwin, and cygwin (v. 1.3.10-1), I'm having some
> horrible problems with inconistent treatment of filenames, especially
> when using (gnu, cygwin) make.  In a nutshell, make seems to be passing
> paths such as "/usr/local/hmake" (etc) to ghc, which is, as I understand
> it, interpretting these in a manner consistent with windows, but not with
> cygwin.  (i.e., it'd expect the above to be something like:
> /cygwin/usr/local/hmake, where the root of the cygwin installation is in
> c:\cygwin.  Experimenting with similar arguments to ghc by hand seems to
> confirm this.
> Is there a work-around for this, or is using cygwin and ghc together just
> an out and out bad idea?
> Cheers,
> Alex.
> _______________________________________________
> Glasgow-haskell-users mailing list