Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 28 Nov 2002 00:34:30 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: ftell() bug Message-ID: <20021128053430.GB29392@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <000301c2969e$1bb1c6f0$0202a8c0@serge> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000301c2969e$1bb1c6f0$0202a8c0@serge> User-Agent: Mutt/1.5.1i On Fri, Nov 22, 2002 at 10:53:56AM +0500, Serge P. Voronin wrote: >I'm find a bug in ftell() while compiling with -mno-cygwin flag (see >attachment). If we compile program without -mno-cygwin flag, then no >bug present. Try compiling the program on linux or unix and see what you get. You'll see that cygwin output from your program agrees with linux or unix. IMO, the windows runtime that Mingw (-mno-cygwin) uses is wrong. However, it doesn't really matter. Cygwin adheres to UNIX conventions. Btw, in the future it would be better to 1) include your test case as text. There is no reason to encode a text file. 2) describe your problem rather than asking others to infer it. cgf -- Please do not send me personal email with cygwin questions or observations. Use the resources at http://cygwin.com/ . -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/