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/
