Jens Mühlenhoff, le Thu 19 Sep 2013 02:18:28 +0200, a écrit : > >Yes. SOCK_CLOEXEC is not currently supported, the TCP/IP stack thinks > >the caller is inventing a new proto type numbered 4194305. You would > >get the same behavior on Linux when building the application against a > >recent libc, but running it against an old kernel without SOCK_CLOEXEC > >support. > > Ok, so libc is reporting a feature the Hurd doesn't support.
Yes, just like in the Linux case. > I was wondering why the Qt code is using (fd != -1 || errno != EINVAL) to > determine success? Because Linux probably returns EINVAL instead of EPROTOTYPE in such an error case. Samuel -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
