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 Message-ID: <3F4676A8.30904@redhat.com> Date: Fri, 22 Aug 2003 16:01:44 -0400 From: "J. Johnston" Organization: Red Hat Inc. User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Corinna Vinschen Cc: cygwin AT cygwin DOT com, newlib AT sources DOT redhat DOT com Subject: Re: How to use __DYNAMIC_REENT__ correctly in multithreaded applications? 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> <20030822193432 DOT GV7858 AT cygbert DOT vinschen DOT de> In-Reply-To: <20030822193432.GV7858@cygbert.vinschen.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Corinna Vinschen wrote: > 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(). > 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. -- Jeff J. -- 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/