Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
From: Shayne Steele <steele AT cs DOT fsu DOT edu>
Message-Id: <200109171623.f8HGNaZ13829@diablo.cs.fsu.edu>
Subject: Unwanted compiler warnings with w32api
To: cygwin AT cygwin DOT com
Date: Mon, 17 Sep 2001 12:23:36 -0400 (EDT)
X-Mailer: ELM [version 2.5 PL5]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Hello

        I recently updated to the latest w32api.  I compile my
programs with gcc and the options '-Wall -W -pedantic', and up until 
the upgrade have had no warnings.  Now I have some 'Extra' warnings

In file included from /usr/include/w32api/windef.h:145,
                 from /usr/include/w32api/windows.h:98,
                 from main-win.c:246:
/usr/include/w32api/winnt.h:1712: warning: ANSI C doesn't support
unnamed structs/unions
/usr/include/w32api/winnt.h:1725: warning: ANSI C doesn't support
unnamed structs/unions

These warnings are annoying.  I just want my own program's warnings not
the w32api warnings.  Last October I complained about the same thing
and someone 'fixed' what needed fixing, and up until now all my
compilations have been warning free (well... at least warning free on 
code I did not write).

-- 
Shayne Steele	    Graduate Student in Computer Science at FSU
steele AT cs DOT fsu DOT edu   http://www.cs.fsu.edu/~steele/
With great abilities come great responsibilities. -- Stan Lee

--
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/