public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org>
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 [thread overview]
Message-ID: <bug-15850-131-RqF9aqrsEk@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15850-131@http.sourceware.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.
next prev parent reply other threads:[~2013-08-19 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 1:13 [Bug network/15850] New: " xiyou.wangcong at gmail dot com
2013-08-19 1:31 ` [Bug network/15850] " bugdal at aerifal dot cx
2013-08-19 18:10 ` carlos at redhat dot com [this message]
2013-08-19 18:40 ` bugdal at aerifal dot cx
2013-08-19 18:52 ` carlos at redhat dot com
2013-08-19 19:43 ` bugdal at aerifal dot cx
2014-01-11 12:51 ` neleai at seznam dot cz
2014-01-12 17:19 ` cvs-commit at gcc dot gnu.org
2014-06-13 9:44 ` fweimer at redhat dot com
2015-02-25 5:14 ` cvs-commit at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-15850-131-RqF9aqrsEk@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).