* Carlos O'Donell <carlos@xxxxxxxxxx> [2017-03-08 10:53:00 -0500]: > On 11/11/2016 07:08 AM, Felix Janda wrote: > > fixes the following compiler errors when <linux/in6.h> is included > > after musl <netinet/in.h>: > > > > ./linux/in6.h:32:8: error: redefinition of 'struct in6_addr' > > ./linux/in6.h:49:8: error: redefinition of 'struct sockaddr_in6' > > ./linux/in6.h:59:8: error: redefinition of 'struct ipv6_mreq' > > Do you have plans for fixing the error when the inclusion order is the other way? the other way (linux header included first) is problematic because linux headers don't follow all the standards the libc follows, they violate namespace rules in their struct definitions, so the libc definitions are necessarily incompatible with them and thus different translation units can end up refering to the same object through incompatible types which is undefined. (even if the abi matches and thus works across the syscall interface, a sufficiently smart toolchain can break such code at link time, and since the libc itself uses its own definitons that's what user code should use too). there should be a way to include standard conform libc headers and linux headers into the same tu, at least the case when all conflicting definitions come from the libc should work and i think that should be the scope of these libc-compat.h changes. (of course if glibc tries to support arbitrary interleavings then the changes should not break that) -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
