From: Andy Wingo <wingo@pobox.com>
To: ilove zfs <ilovezfs@icloud.com>
Cc: 25790-done@debbugs.gnu.org
Subject: bug#25790: SOCK_CLOEXEC and SOCK_NONBLOCK undeclared identifier errors with 2.1.7
Date: Tue, 21 Feb 2017 22:15:27 +0100 [thread overview]
Message-ID: <87ino3xn2o.fsf@pobox.com> (raw)
In-Reply-To: <750c3b96-c1fb-40cb-b208-0dc2a205d283@me.com> (ilove zfs's message of "Sun, 19 Feb 2017 08:18:53 +0000 (GMT)")
On Sun 19 Feb 2017 09:18, ilove zfs <ilovezfs@icloud.com> writes:
> Despite the "accept4 flags. No ifdef as accept4 has a gnulib implementation" building 2.1.7 fails with undeclared identifier errors for SOCK_CLOEXEC and SOCK_NONBLOCK on
> macOS. Wrapping the relevant sections in ifdef SOCK_CLOEXEC and ifdef SOCK_NONBLOCK seems to work around the build failure, but I'm not sure if there are any problems with
> doing this, or why the build isn't correctly taking advantage of the gnulib accept4 implementation.
Yeah sorry about that. Fixed I think (we just don't define
SOCK_NONBLOCK et al now).
Andy
prev parent reply other threads:[~2017-02-21 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 8:18 bug#25790: SOCK_CLOEXEC and SOCK_NONBLOCK undeclared identifier errors with 2.1.7 ilove zfs
2017-02-20 22:06 ` bug#25790: guile-2.1.7 SOCK_CLOEXEC etc Matt Wette
2017-02-21 21:15 ` Andy Wingo [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ino3xn2o.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=25790-done@debbugs.gnu.org \
--cc=ilovezfs@icloud.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).