| > > /tmp/... directory *does* exist, but the \tmp\... directory does | > > not. (And indeed, why should it, since the invocation | didn't ask for | > > it?) | > | > Notice that both GHC and the mingw system calls (the MS provided C | > runtime functions, really) are capable of understanding paths that | > contain either "/" or "\" as directory separators, so | you're reading | > too much into the slashes being reversed in that output message. | | So am I right in thinking that if GHC did no internal | filepath mangling whatsoever, everything file-related would just work? GHC does mangle '/' into '\' on Windows. That is jolly convenient, and we certainly rely on it when using GHC (e.g to build GHC). I don't know why doing so should be a problem; after all, it's Windows. Simon