----- Original Message -----
From: Christopher Faylor <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 10, 2001 5:02 PM
Subject: Re: make -mno-win32 the gcc default?
> On Wed, Jan 10, 2001 at 04:54:26PM -0500, Charles Wilson wrote:
> >Christopher Faylor wrote:
> >>
> >> Earnie has been proposing this and I sort of like the idea but dread
the
> >> potential hue and cry that could result.
> >>
> >
> >I also like the idea, but am terrified of the torrent of "It worked with
> >gcc-2.95.2 and cygwin beta 1.1 [sic]" complaints. Also I'm not sure
> >that all of "my" packages are _WIN32 clean. (For the most part, if they
> >compiled -- I was happy. I didn't look too closely beyond that. I know
> >that zlib and libpng are WIN32 clean 'cause I tested them with
> >-mno-win32. Dunno *for sure* about the rest).
> >
> >> So, is the hue and cry from the lack of WIN32 counterbalanced by
potentially
> >> easier UNIX porting?
> >
> >Ummm....yyyyeeessss....I think????
>
> My sentiments exactly.
>
> We could always make a release, see who complained, and then change it
back if
> it seemed like a bad idea.
>
> cgf
Would it be possible (or desirable) to make it selectable
by the user. Some people might prefer to always have "-mno-win32"
as the default behavior and others might want "-mwin32" and
I'm sure that there are others that might want to switch back
and forth between the two.
--Mark
--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple
