From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1677 invoked by alias); 19 Aug 2013 18:10:24 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Received: (qmail 1643 invoked by uid 48); 19 Aug 2013 18:10:23 -0000 From: "carlos at redhat dot com" To: glibc-bugs@sourceware.org Subject: [Bug network/15850] Glibc headers have conflicts with kernel headers on the definition of struct in6_addr Date: Mon, 19 Aug 2013 18:10:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: network X-Bugzilla-Version: 2.18 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: carlos at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2013-08/txt/msg00088.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=15850 Carlos O'Donell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |carlos at redhat dot com --- Comment #2 from Carlos O'Donell --- (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 . 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.