On Wed, Feb 12, 2003 at 03:06:19AM -0800, Guy Harris wrote: > On Wed, Feb 12, 2003 at 02:39:35PM +1100, Darren Reed wrote: > > Now on this particular linux system, none of the header files in the > > /usr/include directory tree define SA_LEN > > Not even <sys/socket.h>, which, in glibc 2.3 does > > /* Return the length of a `sockaddr' structure. */ > #ifdef _HAVE_SA_LEN > # define SA_LEN(_x) (_x)->sa_len > #else > extern int __libc_sa_len (sa_family_t __af); > extern int __libc_sa_len_internal (sa_family_t __af) attribute_hidden; > # ifndef NOT_IN_libc > # define SA_LEN(_x) INTUSE(__libc_sa_len)((_x)->sa_family) > # else > # define SA_LEN(_x) __libc_sa_len((_x)->sa_family) > # endif > #endif
OK, what about "/usr/include/bits/sockaddr.h" or "/usr/include/bits/socket.h"? Does one of them define SA_LEN and, if so, does that header eventually get included by <sys/socket.h>? On an RH system here, "bits/sockaddr.h" defines SA_LEN, and it's included by "bits/socket.h", which is included by <sys/socket.h>. - This is the TCPDUMP workers list. It is archived at http://www.tcpdump.org/lists/workers/index.html To unsubscribe use mailto:[EMAIL PROTECTED]?body=unsubscribe
