X-Spam-Check-By: sourceware.org Message-ID: <195b3f1f0702011805o51e5d922ldce11e232058ebf7@mail.gmail.com> Date: Fri, 2 Feb 2007 11:05:18 +0900 From: "Wynfield Henman" To: cygwin@cygwin.com Subject: Re: Eliminating -mno-cygwin from gcc? In-Reply-To: <20070201162342.GA17359@trixie.casa.cgf.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20070131131337.GA17256@trixie.casa.cgf.cx> <20070201101648.GD25688@ns1.anodized.com> <20070201103946.GY27843@calimero.vinschen.de> <20070201121552.GB29751@trixie.casa.cgf.cx> <20070201154711.GZ27843@calimero.vinschen.de> <20070201162342.GA17359@trixie.casa.cgf.cx> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com I for one am not adverse to your proposition of separating the ming (mno-cygwin) functionality into its own script or program. This would reduce cygwin gcc's complexity and make it easier to port to cygwin and hopefully, mean nearer gcc versions faster. And by branching off the mno-cygwin, it can be delevoped and maintained at its own pace. As mentioned it will caused some problems with existing build scripts I've written, but in time the bifricated situation will trickle down to be normal in time, I should think. Regards, Henman -------------------------------- RE: On 2/2/07, Christopher Faylor wrote: -- 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/