I've had half an eye on this discussion... just a couple of things to add:
grep: /cygdrive/c/ghc/ghc-5.02.2/bin/ghc: No such file or directory
Ah, yes I think I remember reading once that GHC/mingw32 does not have a driver script, only a directly executable binary. Hence, grepping through the script for configuration information (as hmake-config is attempting to do here) is no longer an option. Unfortunately, I'm not aware of any other way to reliably get config info out of GHC.
'ghc -v' on 5.00 and 5.02 (and later versions) will tell you where the package config file is, and the rest of the info can be extracted from that. However, you do know that we're planning to move to binary interface files, right? Perhaps we should rethink how hmake gets hold of its info about libraries - what exactly does it need to know?
Sadly, the difficulty of using GHC/mingw32 as a bootstrapping compiler seems to be increasing the more we delve into it. Perhaps it would be safest for us simply to recommend GHC/cygwin instead, and disallow the GHC/mingw32 route.
I don't know whether Sigbjorn plans to continue supporting this route - Sigbjorn? Cheers, Simon