Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Sun, 17 Aug 2003 19:05:14 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Question about large file support Message-ID: <20030817170514.GJ3101@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20030817142414 DOT 65546 DOT qmail AT web41507 DOT mail DOT yahoo DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030817142414.65546.qmail@web41507.mail.yahoo.com> User-Agent: Mutt/1.4.1i On Sun, Aug 17, 2003 at 07:24:14AM -0700, ColinB wrote: > I believe that large file support is in version 1.5.0 of Cygwin but Yes. > Are there separate 64-bit versions of fopen/fseek/... called > fopen64/fseek64 as on some platforms, or is there some sort of No. > "transparent" support where you can continue to use fopen/fclose? Yes. > And what is the integer type you need to pass into fseek/fseek64 to > specify 64-bit file offsets? fseek: Only supports long, long is 32 bit. lseek, fseeko: off_t. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/