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: Sat, 22 May 2004 22:54:07 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: ftruncate64() question? Message-ID: <20040523025407.GA5586@coe.bosbc.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <6 DOT 1 DOT 0 DOT 6 DOT 0 DOT 20040521150946 DOT 03262f68 AT pop DOT theworld DOT com> <20040521192359 DOT GA6832 AT coe DOT bosbc DOT com> <20040521203759 DOT GB7790 AT coe DOT bosbc DOT com> <00ba01c43f74$50560f30$64fda287 AT docbill002> <00af01c4403b$42c1c5e0$64fda287 AT docbill002> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <00af01c4403b$42c1c5e0$64fda287@docbill002> User-Agent: Mutt/1.4.1i On Sat, May 22, 2004 at 04:24:22PM -0400, Bill C. Riemers wrote: >> What's wrong with ftruncate? > >ftruncate fails with files larger >= 2GB because off_t gets interpreted as >32 bit signed integer... bash-2.05b$ cat off_t.c #include #include int main (int argc, char **argv) { printf ("sizeof(off_t) = %d\n", sizeof(off_t)); exit (0); } bash-2.05b$ ./off_t sizeof(off_t) = 8 >I can find some archived cygwin messages referencing bug fixes to >ftruncate64 in the cygwin.dll. However, using ftruncate64 results in an >unresolved symbol. You don't use ftruncate64. You use ftruncate. Cygwin is 64 bit by default. >In fact based on those messages, I inserted the following code in my >program as a workaround for a truncate64() function: How about referencing these messages so we'd have some clue as to what you're talking about? cgf -- 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/