This is the mail archive of the
mailing list for the Cygwin project.
RE: [NON-WHINE] RE: mkstemp vs. text mode
- From: "Gary R. Van Sickle" <g dot r dot vansickle at worldnet dot att dot net>
- To: <cygwin-patches at cygwin dot com>
- Cc: <cygwin at cygwin dot com>
- Date: Wed, 19 Apr 2006 21:47:09 -0500
- Subject: RE: [NON-WHINE] RE: mkstemp vs. text mode
More non-negative news: The Cygwin/X Server creates its own subdirectory and
a bunch of files in /tmp and still appears to work fine.
Gary R. Van Sickle
> -----Original Message-----
> From: firstname.lastname@example.org
> [mailto:email@example.com] On Behalf Of Gary R.
> Van Sickle
> Sent: Wednesday, April 19, 2006 8:56 PM
> To: firstname.lastname@example.org
> Cc: email@example.com
> Subject: [NON-WHINE] RE: mkstemp vs. text mode
> > From: Gary R. Van Sickle
> > > From: Gary R. Van Sickle
> > >
> > > > From: Christopher Faylor
> > > [snip]
> > > > Yes, I think it makes sense to open temp files in binary
> > > but I'll bet
> > > > that someone is relying on textmode behavior.
> > >
> > > I'll see that bet and raise you; I'll bet this results in massive
> > > problems.
> > >
> Welp, looks like I (probably) lose that hand (happily). Using:
> CYGWIN_NT-5.1 DFW5RB41 1.5.20s(0.155/4/2) 20060418 12:31:05
> i686 Cygwin
> with a /tmp mounted as text mode works fine for a configure,
> build, and install of wxWindows. The configure does most of
> the temp file machinations, with about 2000 add, modify, and
> remove events in the /tmp directory, as reported by a program
> I have for monitoring such things.
> Gary R. Van Sickle