From 52fb79d6cdecb89a6f0375091e7c12ed79ae6760 Mon Sep 17 00:00:00 2001 From: Florian Weimer Date: Sat, 17 Oct 2015 12:02:37 +0200 Subject: Assume that SOCK_CLOEXEC is available and works This fixes (harmless) data races when accessing the various __have_sock_cloexec variables. --- include/sys/socket.h | 8 -------- 1 file changed, 8 deletions(-) (limited to 'include/sys/socket.h') diff --git a/include/sys/socket.h b/include/sys/socket.h index 2f4bfd3a93..a00ab3cf93 100644 --- a/include/sys/socket.h +++ b/include/sys/socket.h @@ -154,13 +154,5 @@ libc_hidden_proto (__libc_sa_len) # define SA_LEN(_x) __libc_sa_len((_x)->sa_family) #endif -#ifdef SOCK_CLOEXEC -extern int __have_sock_cloexec attribute_hidden; -/* At lot of other functionality became available at the same time as - SOCK_CLOEXEC. Avoid defining separate variables for all of them - unless it is really necessary. */ -# define __have_paccept __have_sock_cloexec -#endif - #endif #endif -- cgit v1.2.3-70-g09d2