X-Spam-Check-By: sourceware.org Date: Thu, 1 Feb 2007 07:14:08 -0500 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Eliminating -mno-cygwin from gcc? Message-ID: <20070201121408.GA29751@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <45C0971E.4080305@byu.net> <20070131132700.GA3478@implementation.labri.fr> <20070131133102.GA17405@trixie.casa.cgf.cx> <20070131134842.GU27843@calimero.vinschen.de> <050901c74547$76f60e20$2e08a8c0@CAM.ARTIMI.COM> <20070131154054.GC19137@trixie.casa.cgf.cx> <17393e3e0701310808s2e8e77d9t638d0e90a83c3ecb@mail.gmail.com> <20070131163221.GD19137@trixie.casa.cgf.cx> 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@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 On Wed, Jan 31, 2007 at 07:24:50PM -0500, Igor Peshansky wrote: >On Wed, 31 Jan 2007, Christopher Faylor wrote: > >> On Wed, Jan 31, 2007 at 10:29:01AM -0600, Matthew Woehlke wrote: >> >Matt Wozniski wrote: >> >>Before simply ripping out support for it, how about just adding a >> >>message to gcc so that when passed "-mnocygwin" on the command line, it >> >>warns that it's deprecated and will be removed in the near future, >> >>before processing? >> > >> >...and add a REALLY BIG MESSAGE that, if something breaks, the person to >> >complain to is the package maintainer and not the Cygwin ML. :-) >> >> No, if something breaks then the user has to fix it. >> >> I don't mind adding a deprecated feature but I think some kind of >> optional wrapper script eliminates the need. > >I agree, except that some people invoke Cygwin's gcc from non-Cygwin >programs, which would present a problem if it were a shell script. >Perhaps we should add some option preprocessing to the gcc executable >itself (which would exec the cross-gcc if -mno-cygwin is present)? Argh. The whole point of this is to eliminate the abomination that is -mno-cygwin from gcc itself. 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". 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/