From: Carlos O'Donell <carlos@xxxxxxxxxxxxxxxx> Date: Wed, 16 Jan 2013 21:15:03 -0500 > +/* If a glibc-based userspace has already included in.h, then we will not > + * define in6_addr (nor the defines), sockaddr_in6, or ipv6_mreq. The > + * ABI used by the kernel and by glibc match exactly. Neither the kernel > + * nor glibc should break this ABI without coordination. > + */ > +#ifndef _NETINET_IN_H > + I think we should shoot for a non-glibc-centric solution. I can't imagine that other libc's won't have the same exact problem with their netinet/in.h conflicting with the kernel's, redefining structures like in6_addr, that we'd want to provide a protection scheme for here as well. Let's pick some more generic names and themes for the CPP macros and comments we use to protect the header file blocks and describe that protection scheme. Thanks. -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list