You were right, Earnie, MinGW-3.2.0rc did not resolve the issue. I know that MinGW is not Cygwin, but this problem was apparently fixed there:
Would it be possible for that fix to be ported to MinGW? I don't know if MinGW normally tracks Cygwin changes or not.
> -----Original Message-----
> Subject: MinGW-users digest, Vol 1 #2489 - 7 msgs
> Message: 4
> I doubt that the
> MinGW-3.2.0 tarball will resolve the issue as it has nothing
> MSYS related.