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: Fri, 22 Aug 2003 22:29:27 +0200 From: Corinna Vinschen To: "J. Johnston" Cc: cygwin@cygwin.com, newlib@sources.redhat.com Subject: Re: How to use __DYNAMIC_REENT__ correctly in multithreaded applications? Message-ID: <20030822202927.GY7858@cygbert.vinschen.de> Mail-Followup-To: "J. Johnston" , cygwin@cygwin.com, newlib@sources.redhat.com References: <3F40EC4D.30704@gmx.net> <3F4134BF.826C3690@redhat.com> <3F41CF80.1030909@gmx.net> <3F466995.9000904@redhat.com> <20030822193432.GV7858@cygbert.vinschen.de> <3F4676A8.30904@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3F4676A8.30904@redhat.com> User-Agent: Mutt/1.4.1i 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 > problem. 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. Corinna -- Corinna Vinschen Cygwin Developer 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/