RE: Has sys/stat.h changed

["Robert Collins" <robert dot collins at itdomain dot com dot au>]

> -----Original Message-----
> From: Earnie Boyd [mailto:earnie_boyd@yahoo.com]
> Sent: Tuesday, 20 February 2001 10:01 AM
> To: cygwin-apps@cygwin.com
> Subject: Re: Has sys/stat.h changed
> 
> 
> Christopher Faylor wrote:
> > 
> > 
> > Unfortunately, they don't use cygwin the way the rest of 
> the net does.
> > 
> > A couple of questions:
> > 
> > 1) Was the defaulting to -mno-win32 a noble but doomed experiment?
> > 
> 
> Noble, yes.  Doomed, no.  I don't think enough have used it since the
> default download is 2.95.2-6.

It makes 100% unix code easier to port, but what are the implications
for mixed code (say for instance code that simultaneously uses cygwin
for socket io, and the windows async file routines for some/all disk io
(something that I'm planning for squid in the near future)).

Depending on those implications, I'm on the doomed side of the fence.
 
> > 2) If we want to stick with -mno-win32 as the default, should gcc
> >    include /usr/include/w32api by default?  I really don't 
> think that
> >    it should but I don't look forward to submitting changes to
> >    the stuff in sources.redhat.com that breaks as a result.
> > 
> 
> Debatable but I'm inclined to leave it out.  If you need it then you
> also need -mwin32.

I agree with Earnie: consistency first. -mno-win32 as default implies
that the win32api is not available. -mwin32 as default implies it is
avaiable. Don't mix n match :]
 
> > 3) Does anyone run this release of gcc as a cross compiler?  Corinna
> >    isn't able to do this but I'm not having any problems 
> building it.
> > 

I run it under win32.

> 
> > If we can clarify the above points, I'll make a 
> gcc-2.95.2-8 release.
> > 
> 
> Hope I have,
> 
> > cgf
> 
> Earnie.
> 


Rob