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: "J. Johnston" <jjohnstn at redhat dot com>
- Cc: cygwin at cygwin dot com, newlib at sources dot redhat dot com
- Date: Fri, 22 Aug 2003 22:29:27 +0200
- Subject: Re: How to use __DYNAMIC_REENT__ correctly in multithreaded applications?
- References: <3F40EC4D.email@example.com> <3F4134BF.826C3690@redhat.com> <3F41CF80.firstname.lastname@example.org> <3F466995.email@example.com> <20030822193432.GV7858@cygbert.vinschen.de> <3F4676A8.firstname.lastname@example.org>
On Fri, Aug 22, 2003 at 04:01:44PM -0400, J. Johnston wrote:
> For clarification, I am not referring to a function, I am referring to the
> struct stat64
> which is needed as an argument to _fstat64_r or _stat64 for that matter.
> There is no struct
> stat64 or struct _stat64 defined externally under Cygwin. The compiler
> fails because
> it does not know the size of the structure. Under linux, the type is
> defined and this is not a
Cygwin has a struct __stat64. We could also define a struct stat64
but this would be contrary to the effort to handle the new structures
transparent. struct __stat64 is struct stat from the applications
point of view.
Red Hat, Inc.
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html