X-Recipient:	archive-cygwin AT delorie DOT com
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:in-reply-to; q=dns; s=
	default; b=T63N1FAU4j8sSrwIvchD3KgebnlLFnXVeVXZ6PvPLTbGyYoW29LAM
	YjwWOBrMTTUpONKK5zDq9omX8IRwt1WXD+oI2h+ah9VB7BOIY/y5ONxNBoNxv/9Z
	wcwicCcfoe1C5m0wNLdCaHVyec7loIwq2SHKlHZCKAycOCmDnS1oOo=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; 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:in-reply-to; s=default;
	bh=eD8pRcAYXgdsVHthniUDERd2iZg=; b=OCbFXI0aU8dJGfT/9LpUq3I37uaP
	J7TnzHxI7qahjR4mTUPcUKueZ53+jbFijcdb20ceEWGeO2r/SW/ACXxzo6EreGG4
	1q/mmoWtBplSQmqA+j1IZSFlZLQPnczuZ+XNLXfA06v53n2epKB8SqhJgfUWN4xQ
	ZVmWLp837x2u0T0=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=1.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	mho-02-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX18TiH4eHCOdaq0MDyrzF7si
Date:	Tue, 15 Oct 2013 15:42:42 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: siginfo_t missing member si_band
Message-ID:	<20131015194242.GA2368@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<525D55B3 DOT 3050002 AT cs DOT utoronto DOT ca>
MIME-Version:	1.0
In-Reply-To:	<525D55B3.3050002@cs.utoronto.ca>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Tue, Oct 15, 2013 at 10:48:19AM -0400, Ryan Johnson wrote:
>Hi all,
>
>While trying to build python3 for cygwin, I kept encountering the 
>following error message:
>
>./Modules/signalmodule.c: In function ?fill_siginfo?:
>./Modules/signalmodule.c:745:60: error: ?siginfo_t? has no member named 
>?si_band?
>PyStructSequence_SET_ITEM(result, 6, PyLong_FromLong(si->si_band));
>^
>Include/tupleobject.h:62:75: note: in definition of macro 
>?PyTuple_SET_ITEM?
>#define PyTuple_SET_ITEM(op, i, v) (((PyTupleObject *)(op))->ob_item[i] 
>= v)
>^
>./Modules/signalmodule.c:745:5: note: in expansion of macro 
>?PyStructSequence_SET_ITEM?
>PyStructSequence_SET_ITEM(result, 6, PyLong_FromLong(si->si_band));
>
>As far as I can tell, siginfo_t::si_band is mandated by POSIX.1-2001, 
>and required for proper handling of SIGPOLL. The latter seems to 
>correspond to async I/O with poll(2). I'm pretty sure cygwin doesn't 
>support async I/O, but shouldn't the struct member at least exist, to 
>avoid breaking code that assumes its existence? The alternative is to 
>patch python3 locally so its os.sigwaitinfo function no longer touches 
>si_band, or to file a bug upstream so that the module's configury tests 
>for its existence before using it.
>
>Thoughts?

Sure.  I question the utility of lying in a structure about the
availability of an unimplemented feature.  If something is specifically
expecting the structure member to exist it seems like it would be
expecting it to do something.

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

- Raw text -