Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date: Wed, 12 Mar 2003 10:53:16 -0500
From: Christopher Faylor <cgf-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin gcc 3.4 and cygwin
Message-ID: <20030312155316.GA14973@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <004801c2e87b$e7bba110$a400a8c0 AT bluebox>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <004801c2e87b$e7bba110$a400a8c0@bluebox>
User-Agent: Mutt/1.5.1i

On Wed, Mar 12, 2003 at 08:43:55PM +1100, Eugene Rosenzweig wrote:
>The latest message in gcc-announce
>http://gcc.gnu.org/ml/gcc-announce/2003/msg00001.html says that
>i?86-*-win32 target will be deprecated as from gcc 3.4 (no date set).

If you look in the gcc list where this was discussed you'll see that *I*
requested the deprecation.  As the cygwin project leader that should
give you some relief.

As others have noted, the cygwin target is i?86-*-cygwin and that's still
available for gcc.  Cygwin is safe.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/