X-Spam-Check-By: sourceware.org Date: Thu, 1 Feb 2007 09:30:57 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Eliminating -mno-cygwin from gcc? Message-ID: <20070201143057.GA15468@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: 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, Feb 01, 2007 at 03:15:54PM +0100, Angelo Graziosi wrote: >Christopher Faylor wrote: > >> If people are calling gcc from non-cygwin apps, then I don't think I >> care too much. We can also provide a sed script to change "gcc >> -mno-cygwin" to "i686-mingw-gcc". > > >... and if they do not like the name "i686-mingw-gcc", they could create >symbolic links "gcc32 --> i686-mingw-gcc", "g77_32 --> i686-mingw-g77" >etc., so they can "make" their project with "CC=gcc32 make" etc.. A symlink isn't going to work with the aforementioned "non-cygwin-programs". 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/