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:	Tue, 17 Dec 2002 11:31:31 -0500
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Gcc 3.2 -mno-cygwin
Message-ID:	<20021217163131.GA19789@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<3500515B75D9D311948800508BA37955014BD67C AT EX-LONDON>
Mime-Version:	1.0
In-Reply-To:	<3500515B75D9D311948800508BA37955014BD67C@EX-LONDON>
User-Agent:	Mutt/1.5.1i

On Tue, Dec 17, 2002 at 02:55:32PM -0000, Vince Hoffman wrote:
>I think you misunderstand. "It adds the "-mno-cygwin" functionality to the
>standard gcc package."
>is just the description of what the gcc-mingw package does. Its what it's
>always done. Its not a new feature, or am i missing something ?

You're not missing anything.  I suggested installing the gcc-mingw package.
Jim noticed that I released a new version of gcc-mingw (amidst a bunch of
other packages) and erroneously thought that his problem was somehow related
to my release.

I do admit that the discussion of gcc-mingw jogged my memory that I had
a new version to release, so I released it.  AFAIK it did not in any way
address any of the problems he was seeing.  As far as I can tell he just
didn't have the package installed.  Even the small amount of detail that
he provided seemed to verify this fact.

I guess we'll never know now.

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/

- Raw text -