This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug network/15850] Glibc headers have conflicts with kernel headers on the definition of struct in6_addr
- From: "carlos at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Mon, 19 Aug 2013 18:10:22 +0000
- Subject: [Bug network/15850] Glibc headers have conflicts with kernel headers on the definition of struct in6_addr
- Auto-submitted: auto-generated
- References: <bug-15850-131 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15850
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #2 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Rich Felker from comment #1)
> We run into this kind of problem with musl quite a bit too, and I don't
> think there's a proper solution except documenting that the kernel headers
> should not be included in userspace except when they provide something that
> has no corresponding libc interface. Any solution in glibc would be either:
>
> A. Specific to certain versions of the kernel headers, and would still leave
> you stuck with problems when using older kernel headers, OR
>
> B. Would cause glibc's headers to be non-conforming (mostly in the sense of
> namespace-pollution) unless you got really lucky with the version of the
> kernel headers you use.
>
> I don't see either of these as reasonable trade-offs. Back in the 90s, glibc
> made the (correct) decision to avoid depending on the kernel headers
> (although it still does in a few places) to provide the standard userspace
> headers. Application developers just need to learn to stop senselessly
> including things from <linux/*.h>.
C. Coordinate.
We can fix this problem but it requires coordination.
I started some work on this and Cong is taking this to completion:
http://sourceware.org/ml/libc-alpha/2013-08/msg00208.html
--
You are receiving this mail because:
You are on the CC list for the bug.