Re: fdopendir closes the file descriptor on MinGW

[Eli Zaretskii]

> Date: Wed, 18 Mar 2015 12:33:57 -0700
> From: Paul Eggert <address@hidden>
> CC: address@hidden
> 
> On 03/18/2015 09:16 AM, Eli Zaretskii wrote:
> > An alternative would be to use Gnulib's opendir instead, which seems
> > to already take care of allocating a file descriptor.  However,
> > Gnulib's opendir is not being linked into the test program; instead,
> > MinGW's own opendir is.
> 
> That doesn't sound right.  The whole point of the dir business on 
> Windows (as I understand it) is to wrap all the directory primitives, 
> and opendir ought to be one of those primitives. Perhaps someone could 
> investigate why the Gnulib opendir isn't being used here, as it should be.

OK, I will take a look.

> > I don't see how Gnulib's dirfd could work for MinGW
> 
> It depends on what one means by "work".

In this case, "work" means make that file descriptor become valid
again.  IOW, it should emulate what happens on Posix systems when
opendir is called: a new file descriptor is allocated.  Otherwise,
fdopendir will still return with the original FD invalid, which was
what triggered this report in the first place.