gio: don't assume that SOCK_CLOEXEC is supported whenever it's defined
authorJulien Cristau <jcristau@debian.org>
Thu, 15 Jul 2010 14:26:02 +0000 (15:26 +0100)
committerDan Winship <danw@gnome.org>
Thu, 15 Jul 2010 22:06:05 +0000 (18:06 -0400)
commit732ff1b27cc6f7bbbb1133bf8e7cb3de8475f72a
tree5b1513efb76db8ea4789bed5d1db6fdb7594bf92
parent8a2d157d49c3dceda029bd0e14f8c7367daa2a36
gio: don't assume that SOCK_CLOEXEC is supported whenever it's defined

Just because SOCK_CLOEXEC was defined at build time doesn't mean the
kernel we're running on supports it.  So if socket() fails with EINVAL,
try again without the flag.

https://bugzilla.gnome.org/show_bug.cgi?id=624463
gio/gsocket.c