[Bug network/15850] Glibc headers have conflicts with kernel headers on the definition of struct in6_addr

["carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>]

http://sourceware.org/bugzilla/show_bug.cgi?id=15850

--- Comment #4 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Rich Felker from comment #3)
> I don't see "C. Coordinate" as an alternative to the problems A and B above.
> The coordination only works with new post-coordination kernel header
> versions (problem A). Assuming glibc is still producing its own definitions
> rather than including the kernel headers (and just turning off its own
> definitions if the kernel version was already included), problem B does not
> occur in the case of strictly conforming applications which are not
> including the linux/*.h headers. However, there's still the possibility of
> unexpected inconsistency for applications which do use linux/*.h.

Sorry Rich, I have had little sleep and I was being a bit tongue-in-cheek here. 

Regardless of how much coordination we have if you have an old system you will
still have "A." (dependence on new glibc and new kernel headers).

I think that "B." will depend largely on the exact headers you are trying to
fix and this is why we're trying to resolve these one at a time for each
header.

However, it is true that in this particular case the glibc headers will choose
specifically not to define certain structures if it is known that kernel header
provides a conforming definition.

> I'm not sure what the intended usage case you're trying to support is. If
> your intent is that the headers roughly match, then it seems like
> applications should not be including the linux ones, and I'm not sure why
> it's more desirable to "support" this case and get it 90-99% "right" instead
> of just documenting that it's wrong (and possibly even using #error to
> correct this bad practice).

It's not wrong, and we should support it.

What do we loose by coordinating the two sets of headers?

-- 
You are receiving this mail because:
You are on the CC list for the bug.