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: Wed, 28 Feb 2001 15:59:23 -0500 From: Christopher Faylor To: cygwin-apps AT cygwin DOT com Subject: Re: gcc questions prior to -8 release Message-ID: <20010228155923.B4675@redhat.com> Reply-To: cygwin-apps AT cygwin DOT com Mail-Followup-To: cygwin-apps AT cygwin DOT com References: <20010219213847 DOT F23112 AT redhat DOT com> <20010228085315 DOT L449 AT dothill DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <20010228085315.L449@dothill.com>; from Jason.Tishler@dothill.com on Wed, Feb 28, 2001 at 08:53:15AM -0500 On Wed, Feb 28, 2001 at 08:53:15AM -0500, Jason Tishler wrote: >On Mon, Feb 19, 2001 at 09:38:47PM -0500, Christopher Faylor wrote: >> 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. > >Have we reached closure on the above? > >I can build the current Python CVS with gcc 2.95.2-6 but not 2.95.2-7 >unless I specify -I/usr/include/w32api. Will the "extra" option be >needed for 2.95.2-8 and later too? The majority of people liked the -7 behavior which was to avoid adding /usr/include/w32api to the search path unless -mwin32 was specified, so that's what I'll be doing in -8. cgf