public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <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:40:00 -0000 [thread overview] Message-ID: <bug-15850-131-luiHUIfd9a@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15850-131@http.sourceware.org/bugzilla/> http://sourceware.org/bugzilla/show_bug.cgi?id=15850 --- Comment #3 from Rich Felker <bugdal at aerifal dot cx> --- 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. 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). -- 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:40 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 2013-08-19 18:40 ` bugdal at aerifal dot cx [this message] 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-luiHUIfd9a@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: linkBe 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).