Hi,
wanted to point out that checking if SOCK_CLOEXEC is defined as done in
https://github.com/libusbx/libusbx/commit/242d49c636b390d64740b79953c68c2b28cae8ff
is not enough. SOCK_CLOEXEC might be defined in one of the libc-headers (libc
= glibc, uClibc, etc.) but actually not supported by the kernel version used.
See this
[dbus-code](http://cgit.freedesktop.org/dbus/dbus/tree/dbus/dbus-sysdeps-unix.c?id=4df8738794422c216b25e1bc1bbc80654c948c5d#n140)
or [this
libusb-patch](http://freetz.org/browser/trunk/make/libs/libusb1/patches/020-kernel_below_2.6.27_support.libusb1.patch?rev=10904)
(based on dbus code and successfully used in
[freetz](http://freetz.org)-project) for the inspiration on how to handle the
issue properly ;-)
Best,
Gene
---
Reply to this email directly or view it on GitHub:
https://github.com/libusbx/libusbx/issues/124#issuecomment-22079186
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
libusbx-devel mailing list
libusbx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libusbx-devel
