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: Fri, 22 Aug 2003 21:34:32 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com, newlib AT sources DOT redhat DOT com Subject: Re: How to use __DYNAMIC_REENT__ correctly in multithreaded applications? Message-ID: <20030822193432.GV7858@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com, newlib AT sources DOT redhat DOT com References: <3F40EC4D DOT 30704 AT gmx DOT net> <3F4134BF DOT 826C3690 AT redhat DOT com> <3F41CF80 DOT 1030909 AT gmx DOT net> <3F466995 DOT 9000904 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F466995.9000904@redhat.com> User-Agent: Mutt/1.4.1i On Fri, Aug 22, 2003 at 03:05:57PM -0400, J. Johnston wrote: > A monster patch has been checked in. I found a problem in > stdio64/fseeko64.c > using struct stat when calling _fstat64_r. I could not switch to use stat64 > as Cygwin has not defined it externally. For now, stdio64/fseeko64.c will > use _fstat_r > instead of _fstat64_r. What about _stat64, which is defined externally. I don't understand the rule, in which case newlib calls foo() and in which case it calls _foo(). 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/