pps. ah, silly me. i finally understand that ghc ticket #1280 is not a
ghc issue at all. if gcc depends on that same call, it will not see the
mingw ld as executable, so might fall back on defaults later in the
PATH, right? but that would make me wonder how anyone could
have a vista build of ghc? perhaps they are using a newer mingw/gcc,
with some workaround for the issue? well, i'll stop guessing here.
there we go: http://sourceforge.net/forum/forum.php?forum_id=679462
..
* include/io.h (__mingw_access): New static inline wrapper to
restore pre-Vista 'access (fname, X_OK)' behaviour.
(__USE_MINGW_ACCESS): Use to map access() to
__mingw_access().
..
that looks promising, doesn't it?
claus
_______________________________________________
Haskell-Cafe mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/haskell-cafe
