From: Eric Blake <eblake@redhat.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.4.0-0.11
Date: Thu, 17 Dec 2015 21:16:00 -0000 [thread overview]
Message-ID: <56732621.6040101@redhat.com> (raw)
In-Reply-To: <20151217210107.GC3507@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 1809 bytes --]
On 12/17/2015 02:01 PM, Corinna Vinschen wrote:
>> Here's what happens:
>>
>> One of the Gnulib modules includes sys/types.h, which includes sys/select.h
>> because of the recent changes. This brings in Gnulib's sys/select.h, which
>> includes signal.h. We then get the errors I posted because we haven't yet
>> finished including sys/types.h.
Gnulib has been taught to work around early inclusion problems before;
sounds like this will be another case where gnulib has to make sure the
system header is complete before its own replacements kick in.
>>
>> All the build errors disappear if I remove '#include <sys/select.h>' from
>> sys/types.h. You said above that the macros related to select don't really
>> belong in sys/types.h. So why does the latter include sys/select.h?
>
> Because it's done exactly the same way on FreeBSD and OpenBSD:
>
> # if __BSD_VISIBLE
> #include <sys/select.h>
> [...]
>
> Gnulib should allow to work with this to be portable. So why does gnulib
> provide its own sys/select.h? Is it configurable?
I'll raise this on the gnulib list, and we can come up with workarounds.
But bypassing gnulib's sys/select.h probably won't work in general
(gnulib tends to always provide wrapper headers that use #include_next
to the system header, even if nothing is replaced, because it is easier
than trying to figure out when a wrapper header is needed). Of course,
fixing it in gnulib won't help the myriad of projects that will be
bitten by this until they do a new release based on updated gnulib, so
maybe we can also find a way to make cygwin play nice without a gnulib
update required. I'm still investigating.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2015-12-17 21:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-16 16:48 Corinna Vinschen
2015-12-16 18:25 ` Ismail Donmez
2015-12-16 23:13 ` Ken Brown
2015-12-17 9:36 ` Corinna Vinschen
2015-12-17 18:47 ` Ken Brown
2015-12-17 20:17 ` Corinna Vinschen
2015-12-17 20:39 ` Ken Brown
2015-12-17 21:01 ` Corinna Vinschen
2015-12-17 21:16 ` Eric Blake [this message]
2015-12-17 21:41 ` Eric Blake
2015-12-17 21:56 ` 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=56732621.6040101@redhat.com \
--to=eblake@redhat.com \
--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).