X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Message-ID: <49C6DADF.90305@gmail.com>
Date: Mon, 23 Mar 2009 00:42:07 +0000
From: Dave Korn <dave DOT korn DOT cygwin AT googlemail DOT com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: PING: Deprecation of -mno-cygwin.
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.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



    Ho there gang.  Over on gcc-patches, Kai has posted a patch to add some
documentation for the i386 cygming subtarget options.  See the thread at:

  http://gcc.gnu.org/ml/gcc-patches/2009-03/threads.html#00994

  I asked him if he would add a note mentioning that -mno-cygwin is
deprecated, and anyone who wants to review the patch or suggest wording for
the deprecation warning is invited to pitch in to that thread.  (In
particular, should we describe -mcygwin as being deprecated too, or should we
say that it will become the always-on default setting, but not actually
removed, since we might want to retain the positive form as a permitted no-op
flag to aid backward compatibility with old makefiles that use it?)

    cheers,
      DaveK



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