From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: GCC-6.4 sys/select.h build failures with std=c++14
Date: Tue, 26 Sep 2017 05:33:00 -0000 [thread overview]
Message-ID: <5cacbf9c-26d0-da8b-0aa8-ad5ec50bea2d@gmail.com> (raw)
In-Reply-To: <CAHBhQykTn7Y2rPVtAQSaVu+1J8ytSDAAcT-Su5e_oABEVNmtrA@mail.gmail.com>
On 26/09/2017 03:41, Ian Fette wrote:
> I tried compiling a very simple program with curl using -std=c++14 under
> 64-bit cygwin with gcc 6.4.0. When compiling with just g++ main.cpp -lcurl
> everything is fine, however if I try to use c++14 as the dialect (g++
> main.cpp -lcurl -std=c++14) familiar problems creep up
>
> In file included from /usr/include/curl/curl.h:2547:0,
> from main.cpp:10:
> /usr/include/curl/multi.h:155:40: error: âfd_setâ has not been declared
> fd_set *read_fd_set,
> ^~~~~~
> /usr/include/curl/multi.h:156:40: error: âfd_setâ has not been declared
> fd_set *write_fd_set,
> ^~~~~~
> /usr/include/curl/multi.h:157:40: error: âfd_setâ has not been declared
> fd_set *exc_fd_set,
> ^~~~~~
>
>
> This is resolved by manually including <sys/select.h> before including
> <curl/curl.h>
>
this seems more an issue of curl header as from
http://pubs.opengroup.org/onlinepubs/009696899/basedefs/sys/select.h.html
"The <sys/select.h> header shall define the fd_set type as a structure."
so if they are using it, they should have a proper include
Marco
--
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 prev parent reply other threads:[~2017-09-26 5:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 1:41 Ian Fette
2017-09-26 4:49 ` Brian Inglis
2017-09-26 5:33 ` Marco Atzeri [this message]
2017-09-26 19:33 ` Hans-Bernhard Bröker
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=5cacbf9c-26d0-da8b-0aa8-ad5ec50bea2d@gmail.com \
--to=marco.atzeri@gmail.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).