Re: fseek064 calling fflush on Cygwin

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Brian Ford on 7/13/2007 11:50 AM: >> So much for 'early next week'. Here's the full patch - okay to apply? > > I appreciate the effort, but I think you sent this to the wrong list ;-). > Thanks again. That, and I forgot to attach the pa

Re: fseek064 calling fflush on Cygwin

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Eric Blake on 6/22/2007 2:26 PM: >> So, it would seem that fflush is not 64 bit safe and fseeko64 should not >> be calling it, but I'm not sure how to fix it. >> > In environments with large files, fflush needs to check for __SL64, in whic

Re: fseek064 calling fflush on Cygwin

Brian Ford FlightSafety.com> writes: > > I have an application that is having a 64-bit file I/O problem with Cygwin > 1.7.0 CVS that it did not have with Cygwin 1.5.18. I have tracked it > down to the following series of calls in newlib: > > #0 fflush (fp=0x7b5a764) > at ../../../../../cy

fseek064 calling fflush on Cygwin

I have an application that is having a 64-bit file I/O problem with Cygwin 1.7.0 CVS that it did not have with Cygwin 1.5.18. I have tracked it down to the following series of calls in newlib: #0 fflush (fp=0x7b5a764) at ../../../../../cygwin/newlib/libc/stdio/fflush.c:124 #1 0x611049ff in