DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:content-transfer-encoding
	:in-reply-to; q=dns; s=default; b=dRjJSKS/YY9Tk1QFaKjajFCjQYzyR3
	+1yqreEgy36IH6JwbkhwZQrIqV22NIa80Sp5UoCn4ESLUJMOyNzGNOr9XASCM6E9
	5+XXGmoXYQMFMr8tz87E6IPNGKF7ui7qHO18Rx/dH6YqBx7a9upf8MuCT9SiH3he
	oNleubgLe7GQY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Wed, 24 Apr 2013 20:12:48 +0200
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Redefinition of `struct in6_addr'?
Message-ID: <20130424181248.GA26397@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <CAEE3Wrm8MwsN2MMNTRGdLgJvSHPnusJN-TXZrJFL-26BtrW_ng@mail.gmail.com> <20130424154409.GX26397@calimero.vinschen.de> <CAEE3Wrm4iARi33g3gOqfbyJ_Jwc6phQ8xNZSQ6=Cknj-bUQ1-g@mail.gmail.com> <CE9C056E12502146A72FD81290379E9A6095C4FA@ENFIRHMBX1.datcon.co.uk> <CAEE3Wr=cDmAKuJ5rDK0wYoW9hVYzdfTnXCvjVMUhe0qgC4kzGA@mail.gmail.com> <20130424175107.GZ26397@calimero.vinschen.de> <20130424175359.GH5968@type.youpi.perso.aquilenet.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20130424175359.GH5968@type.youpi.perso.aquilenet.fr>
User-Agent: Mutt/1.5.21 (2010-09-15)

On Apr 24 19:53, Samuel Thibault wrote:
> Corinna Vinschen, le Wed 24 Apr 2013 19:51:07 +0200, a écrit :
> > > > /usr/include/cygwin/in6.h:75:8: error: redefinition of ‘struct in6_addr’
> > > > /usr/lib/gcc/i686-pc-cygwin/4.5.3/../../../../include/w32api/in6addr.h:17:16:
> > > > note: originally defined here
> > 
> > Don't know this file but this is a bug in config.h.  struct in6_addr
> > is defined in a system header, so it should not be gratuitously defined 
> > in a project header, especially if the definition collides with the
> > right one from the system header.
> 
> Mmm, but here it's w32api definition vs cygwin definition.

Maybe I didn't read it exactly, but the bottom line here is, when
building for Cygwin, either use the POSIX network headers (preferredly),
or use winsock.h.  Mixing them is not supported.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple