Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Date: Sat, 17 Mar 2001 17:28:30 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-apps AT cygwin DOT com
Subject: gcc 2.95.3-1 and -mwin32
Message-ID: <20010317172830.A24346@redhat.com>
Reply-To: cygwin-apps AT cygwin DOT com
Mail-Followup-To: cygwin-apps AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i

I've got gcc 2.95.3-1 ready to go.  It seems to work ok.

I've had a private discussion with DJ about the affect of -mwin32.  We
both feel that the windows header files should be included regardless of
whether this switch is included or not.  I think that Chuck Wilson also
persuasively argued this point.

If we don't do this, then there are a lot of gratuitous changes required
for a lot of configurations.  I've had to change four or five directories
on sources.redhat.com alone.

So, while I appreciate all of the work that Robert Collins is doing to get
things working in autoconf, I've come to believe that the marginal benefits
of not including /usr/include/w32api outweigh the drawbacks.

So, unless someone has a strong objection, the default for gcc 2.95.3-1,
gcc 3.0, and gcc 3.1 will be to include /usr/include/w32api.

I'll wait a couple of days to see if anyone has any strong objections
before I release the new version of gcc.

cgf