Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com List-Subscribe: List-Archive: List-Post: List-Help: , Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com Date: Sat, 17 Mar 2001 18:07:03 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: gcc 2.95.3-1 and -mwin32 Message-ID: <20010317180703.A23000@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <20010317172830 DOT A24346 AT redhat DOT com> <3AB3ECE7 DOT 26B3D8D3 AT ece DOT gatech DOT edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <3AB3ECE7.26B3D8D3@ece.gatech.edu>; from cwilson@ece.gatech.edu on Sat, Mar 17, 2001 at 06:01:59PM -0500 On Sat, Mar 17, 2001 at 06:01:59PM -0500, Charles S. Wilson wrote: >Christopher Faylor wrote: >> >> I've got gcc 2.95.3-1 ready to go. It seems to work ok. > >[snip] > >> So, unless someone has a strong objection, the default for gcc 2.95.3-1, >> gcc 3.0, and gcc 3.1 will be to include /usr/include/w32api. > >Q: Does that also mean that the default for gcc-2.95.3-1 on cygwin will >be to #define WIN32 & WINDOWS in addition to merely including >/usr/include/w32api in the include path? e.g. that -mwin32 is the >default now (again)? I wasn't planning on doing this, no. I still think that Cygwin should not define these unless asked. This does cause problems for some of the stuff in sources.redhat.com but they are minor compared to the effort of adding -mwin32 everywhere that it was needed. So, this is still different from gcc-2.95.2-1. cgf