Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: Uwe Bonnes MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 21 Mar 2000 19:21:42 +0100 (MET) To: Mumit Khan Cc: cygwin@sourceware.cygnus.com Subject: Re: Status of inclusion of Cygwin/MingW into Main GCC In-Reply-To: <200003211813.MAA24795@hp2.xraylith.wisc.edu> References: <14551.45820.845769.235806@hertz.ikp.physik.tu-darmstadt.de> <200003211813.MAA24795@hp2.xraylith.wisc.edu> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14551.48440.733035.900081@hertz.ikp.physik.tu-darmstadt.de> Mumit Khan writes: > GCC for all x86-win32 targets is still evolving, and the changes that > we've made to gcc-2.95.x branch will NOT make it into the official gcc > release branch (the release branch is frozen for new features). Most > of these changes are incorporated into the mainline gcc, ie., the > development branch, and will show up in the next major release. > > Since we provide full sources, and will provide full diffs if requested, > I don't see this as a problem. The alternative is of course to cripple > our gcc releases and only provide what's in the official gcc-2.95.2 > release. That is not likely to happen. > > The GCC sources you get from the Cygwin/Mingw/etc release is simply a > superset of what you get in official gcc-2.95.2 release. I use that to > build our 10 or so targets, and do test it for regression to make sure > we're not crippling other host/target combinations. > Thanks for the clarification! Bye Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ---------- -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com