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, 27 Aug 2002 23:15:29 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [gcc-3.2]: mbstate_t defined by gcc conflicts with cygwin header _types.h
Message-ID: <20020828031529.GA26064@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20020827202906 DOT 72517 DOT qmail AT web21009 DOT mail DOT yahoo DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20020827202906.72517.qmail@web21009.mail.yahoo.com>
User-Agent: Mutt/1.3.23.1i

On Tue, Aug 27, 2002 at 01:29:06PM -0700, Nicholas Wourms wrote:
>Hi,
>
>I was joining in the fun of compiling xerces with the new gcc-3.2 and
>the latest cygwin build from cvs.  Midway through I happened upon
>this:
>
>
>/usr/include/c++/3.2/cwchar:65: conflicting types for `typedef struct
>mbstate_t 
>   mbstate_t'
>/usr/include/sys/_types.h:41: previous declaration as `typedef struct
>
>   _mbstate_t mbstate_t'
>
>A quick look at the package search shows that this file is unique to
>gcc-3.2 and not earlier versions.   I also assume, based on the fact
>that Abe and Gerrit have sucessfully built it, that this is a gcc-3.2
>related issue.  The questions that come to mind are:
>
>1)Should the Cygwin header be changed?
>2)Should the g++ header be changed?

This one.  It's a configury bug in libstdc++.  I think I fixed it.

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/