public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adconrad at 0c3 dot net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/15544] move idtype_t definition into sysdeps (bits) directory
Date: Fri, 20 Dec 2013 03:32:00 -0000 [thread overview]
Message-ID: <bug-15544-131-RD1Xj56iRY@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15544-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15544
Adam Conrad <adconrad at 0c3 dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |adconrad at 0c3 dot net
--- Comment #2 from Adam Conrad <adconrad at 0c3 dot net> ---
So, worth noting on this that the Linux kernel and glibc have different ideas
about P_ALL, P_GID, and P_PID. This has gone unnoticed for a long time
probably due to a fluke in header ordering, but this slight change has made
anyone who includes <linux/keyboard.h> explode. So far, we've seen that with
sdl and kbd.
Not sure who is "right" and "wrong" here, but I'm inclined to say that
linux/wait.h is probably the wrong one. Either way, it should be sorted on one
side or the other.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-12-20 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 16:46 [Bug libc/15544] New: " Petr.Salinger at seznam dot cz
2013-05-28 19:44 ` [Bug libc/15544] " Petr.Salinger at seznam dot cz
2013-12-20 3:32 ` adconrad at 0c3 dot net [this message]
2014-06-13 17:35 ` fweimer at redhat dot com
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-15544-131-RD1Xj56iRY@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).