After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 141253 - poll(2) is in <poll.h>, not <sys/poll.h> per SUS standard
poll(2) is in <poll.h>, not <sys/poll.h> per SUS standard
Status: RESOLVED WONTFIX
Product: pkg-config
Classification: Deprecated
Component: general
unspecified
Other All
: Low enhancement
: ---
Assigned To: Tollef Fog Heen
pkg-config qa
Depends on: 141251
Blocks:
 
 
Reported: 2004-04-28 02:16 UTC by Todd Vierling
Modified: 2008-04-28 20:04 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Todd Vierling 2004-04-28 02:16:04 UTC
The following is the same as Bug 141252 for GLib1 or Bug 141251 for GLib2.  It
is also present in pkg-config, as that includes a mini-copy of GLib1.

Compile GLib or GLib2 on Interix 3.5, which has <poll.h> but no <sys/poll.h>. 
Fail because the poll() symbol was found by "configure", but no header file was
included when compiling gmain.c to get the POLL* constants and prototype.

The Single Unix Specification standard explicitly states that these definitions
are in <poll.h>, not <sys/poll.h>.  But, it's possible that older systems only
have <sys/poll.h>.

Fix: Add "poll.h" to the list of headers searched in configure.in, and if
present (HAVE_POLL_H), use that *in preference to* <sys/poll.h> in gmain.c.
Comment 1 Todd Vierling 2004-04-28 14:16:31 UTC
It turns out that poll(2) is nonfunctional as of Interix 3.5 anyway, so I've
bumped the priority on this way down.

The issue still stands as standards noncompliance, but that's more of an
enhancement request.
Comment 2 James Henstridge 2005-04-12 02:07:09 UTC
Reassigning open pkg-config bugs to Tollef Fog Heen (the new pkg-config
maintainer), so he can triage them.
Comment 3 Tollef Fog Heen 2008-04-28 20:04:23 UTC
Given that I don't think glib 1.x is going to be updated for this, ever, I'm closing this bug as wontfix.