X-Spam-Check-By: sourceware.org Date: Thu, 27 Apr 2006 18:06:44 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Fixing the state of C++ in Cygwin Message-ID: <20060427220644.GB11193@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <000001c669f1$88a72cd0$a501a8c0 AT CAM DOT ARTIMI DOT COM> <44513EE5 DOT 53E528AB AT dessent DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44513EE5.53E528AB@dessent.net> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On Thu, Apr 27, 2006 at 03:00:05PM -0700, Brian Dessent wrote: >-mno-cygwin ought to work fine from the stock FSF sources I'm told >(provided of course that you build it twice, once as i686-pc-cygwin and >then again as i686-pc-mingw and install them to the same prefix.) I would hope that it does by now. I certainly hacked on it enough over the years and, unless Gerrit has been holding out on me, all of the appropriate changes are in the gcc mainline. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/