X-Spam-Check-By: sourceware.org
Date: Wed, 31 Jan 2007 19:24:50 -0500 (EST)
From: Igor Peshansky <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: Eliminating -mno-cygwin from gcc?
In-Reply-To: <20070131163221.GD19137@trixie.casa.cgf.cx>
Message-ID: <Pine.GSO.4.63.0701311917170.4318@access1.cims.nyu.edu>
References: <20070131131337 DOT GA17256 AT trixie DOT casa DOT cgf DOT cx> <45C0971E DOT 4080305 AT byu DOT net>  <20070131132700 DOT GA3478 AT implementation DOT labri DOT fr> <20070131133102 DOT GA17405 AT trixie DOT casa DOT cgf DOT cx>  <20070131134842 DOT GU27843 AT calimero DOT vinschen DOT de> <050901c74547$76f60e20$2e08a8c0 AT CAM DOT ARTIMI DOT COM>  <20070131154054 DOT GC19137 AT trixie DOT casa DOT cgf DOT cx>  <17393e3e0701310808s2e8e77d9t638d0e90a83c3ecb AT mail DOT gmail DOT com>  <epqg4d$h8d$1 AT sea DOT gmane DOT org> <20070131163221 DOT GD19137 AT trixie DOT casa DOT cgf DOT cx>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 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)?

> And, I really think that we should consider adding some kind of way
> to warn people about these issues in setup.exe.  I've always thought that
> it should be somehow possible for packages to open dialog boxes.

FWIW, I've been toying with the idea of setup keeping an open pipe that
postinstall scripts could write to, so that any messages coming via that
pipe are displayed as dialog boxes...  It probably won't help in this
particular case, since you'd want to see this information *before*
installing the package.

Another thing that I was thinking of doing was some way of displaying the
release notes (or at least the announcement message) for the selected
package.  However, that will require either reworking the chooser or
adding the popup menu functionality to it, as well as some system on
sourceware to keep track of the announcement messages (also proposed but
never implemented).  Anyone want to take a shot at the popup menu
implementation in the chooser?

The followups to the last couple of paragraphs probably belong on
cygwin-apps...
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha AT cs DOT nyu DOT edu | igor AT watson DOT ibm DOT com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

Freedom is just another word for "nothing left to lose"...  -- Janis Joplin

--
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/