This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: How to use __DYNAMIC_REENT__ correctly in multithreaded applications?

On Mon, Aug 25, 2003 at 02:25:07PM -0400, J. Johnston wrote:
> Corinna Vinschen wrote:
> >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.
> Where in particular?  I have tried this as well.  Having it defined as 
> empty is of no help.
> The compiler needs to know its size and access one of the fields.
> With struct __stat64 st;
> /home/jjohnstn/sourceware/src/newlib/libc/stdio64/fseeko64.c: In function 
> `_fseeko64_r':
> /home/jjohnstn/sourceware/src/newlib/libc/stdio64/fseeko64.c:112: storage 
> size of `st' isn't known

struct __stat64 is guarded by an #ifdef __INSIDE_CYGWIN__.

You must either #define __INSIDE_CYGWIN__ or
winsup/cygwin/include/cygwin/stat.h must change to

  #if defined (__INSIDE_CYGWIN__) || defined (_COMPILING_NEWLIB)

I guess the latter is the better approach.


Corinna Vinschen
Cygwin Developer
Red Hat, Inc.

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]