Alex Ferguson <[EMAIL PROTECTED]> writes:
> (This was all motivated, btw, by trying to build HaXml under ghc/cygwin,
> which fell for me at the first hurdle of "first catch your hmake" in the
> recipe. I've now gotten as far as a _build_ of hmake, but it then runs
> into similar issues with its o
Thank you Claus! I've incorporated your section exactly as written.
It'll be in the next release of GHC.
Simon
| -Original Message-
| From: Claus Reinke [mailto:[EMAIL PROTECTED]]
| Sent: 31 January 2003 00:40
| To: [EMAIL PROTECTED]
| Subject: Re: ghc/cygwin filename resolu
> Alex
>
> As Simon M says, if you (or anyone else) felt able to write up a
> standalone summary
> of what the problem is, and what the solution is, I'd love to add it to
> the GHC
> FAQ or documentation somewhere. In my experience, simply explaining the
> problem
> clearly is quite tricky. (E.g.
>As Simon M says, if you (or anyone else) felt able to write up a
>standalone summary of what the problem is, and what the solution is, I'd love
>to add it to the GHC FAQ or documentation somewhere.
Following the worse-is-better approach, here's some text for others
to fiddle with (I'd recommen
in vs mingw issues, described in
the Building Guide,
took me ages to understand well enough to write down.)
Simon
| -Original Message-
| From: Alex Ferguson [mailto:[EMAIL PROTECTED]]
| Sent: 29 January 2003 16:29
| To: [EMAIL PROTECTED]
| Subject: Re: ghc/cygwin filename resolution
Thanks to all for the replies; Hal's resolution rings a bell, now that
I think about it, from Ye Olde Days when cygwin was a ghc pre-req -- just
didn't think of it when installing more recently on a new machine. (Install
in haste, repent at leisure.) Claus' suggestion about relative paths
does
Alex wrote
[snip]
> 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, a
> {another candidate for the ghc faq?-}
By all means - or possibly the section of the Building Guide devoted to
Win32 builds. Would anyone like to write a concise description of the
filename issues on Windows/cygwin/GHC for the docs?
I'm certainly not an expert here, but I believe the problems
> 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
> i
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 abou
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, interp
11 matches
Mail list logo
