This is the mail archive of the
mailing list for the Cygwin project.
Re: How to use __DYNAMIC_REENT__ correctly in multithreaded applications?
- From: Corinna Vinschen <vinschen at redhat dot com>
- To: cygwin at cygwin dot com, newlib at sources dot redhat dot com
- Date: Fri, 22 Aug 2003 21:34:32 +0200
- Subject: Re: How to use __DYNAMIC_REENT__ correctly in multithreaded applications?
- References: <3F40EC4D.firstname.lastname@example.org> <3F4134BF.826C3690@redhat.com> <3F41CF80.email@example.com> <3F466995.firstname.lastname@example.org>
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
> 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 Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:email@example.com
Red Hat, Inc.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html