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:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; q=dns; s=default; b=T7eI8BXouKuXy+uDWY/pa++6Q3uRSGjTRR9+8d+Rgjp OUkJMkryfZa705mKcsCdVsfPPM7hYontkgTdo/pxoO1gsUFzZTPX11fQMSkFRIyc oWuN6Fgtwvz40tst7ba7tsD4AjaoFUAty9XdzysFNCIYfYZAqosg2ohHCV2GfD+Y = 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:message-id:date:from:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; s=default; bh=RHLINQSE/gl3r7HxIIoUnSAQs9w=; b=sCArCfcj5SwM+5RxG 7YuKwZuF1uTRNCVNjt1ZzeJ3jlxa49RyT54APnusZq2VsysWVP63yW7ns+Ct33Up P/mbR9yM8XI+H4B7zAyGtblCHWQjptro2ChJ71W6+nyGd246BSVkppDFnIRUCtDs vJlfUD7ANtZr02FF6Fxdy5jJEU= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_LOW,RP_MATCHES_RCVD,SPF_NEUTRAL autolearn=ham version=3.3.2 X-HELO: bureau85.ns.utoronto.ca Message-ID: <525DB015.1010707@cs.utoronto.ca> Date: Tue, 15 Oct 2013 17:13:57 -0400 From: Ryan Johnson User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: siginfo_t missing member si_band References: <525D55B3 DOT 3050002 AT cs DOT utoronto DOT ca> <20131015194242 DOT GA2368 AT ednor DOT casa DOT cgf DOT cx> In-Reply-To: <20131015194242.GA2368@ednor.casa.cgf.cx> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes On 15/10/2013 3:42 PM, Christopher Faylor wrote: > 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. So that would be a vote for filing a bug upstream with python's FFI interface to signal handling? Fair enough. Ryan -- 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