From: Ryan Johnson <ryan.johnson@cs.utoronto.ca>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: siginfo_t missing member si_band
Date: Tue, 15 Oct 2013 14:48:00 -0000 [thread overview]
Message-ID: <525D55B3.3050002@cs.utoronto.ca> (raw)
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?
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
next reply other threads:[~2013-10-15 14:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-15 14:48 Ryan Johnson [this message]
2013-10-15 19:42 ` Christopher Faylor
2013-10-15 21:14 ` Ryan Johnson
2013-10-15 22:36 ` Christopher Faylor
2013-10-15 23:15 ` Larry Hall (Cygwin)
2013-10-15 23:16 ` Warren Young
2013-10-16 7:59 ` Corinna Vinschen
2013-10-16 21:27 ` Christopher Faylor
2013-10-17 3:46 ` Ryan Johnson
2013-10-17 8:48 ` Corinna Vinschen
2013-10-16 13:17 ` Bengt Larsson
2013-10-16 16:05 ` Corinna Vinschen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=525D55B3.3050002@cs.utoronto.ca \
--to=ryan.johnson@cs.utoronto.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).