Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <20020827202906.72517.qmail@web21009.mail.yahoo.com> Date: Tue, 27 Aug 2002 13:29:06 -0700 (PDT) From: Nicholas Wourms Subject: [gcc-3.2]: mbstate_t defined by gcc conflicts with cygwin header _types.h To: cygwin AT cygwin DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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? 3)Should xerces define MBSTATE_T? Not that this is necessarily a bug report, just thought I put it out there to see what the others think. Cheers, Nicholas __________________________________________________ Do You Yahoo!? Yahoo! Finance - Get real-time stock quotes http://finance.yahoo.com -- 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/