public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vapier at gentoo dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/9685] __have_{sock_cloexec,pipe2} checks not valid with linux headers older than 2.6.27 Date: Sat, 07 Feb 2009 06:28:00 -0000 [thread overview] Message-ID: <20090207062843.8775.qmail@sourceware.org> (raw) In-Reply-To: <20081227035150.9685.vapier@gentoo.org> ------- Additional Comments From vapier at gentoo dot org 2009-02-07 06:28 ------- umm, there's two parts here: first, the original report where glibc is broken on *all* arches, even when you want to put on your "supported" goggles. second: you're turning the __ASSUME_XXX code into "only works on supported arches". yes, other arches can disable the __ASSUME_XXX stuff completely, but that sort of defeats the entire purpose of it. even if you choose to wrongly ignore the second part (which i imagine you will), there's still the matter of the first -- What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|WONTFIX | http://sourceware.org/bugzilla/show_bug.cgi?id=9685 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2009-02-07 6:28 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-27 3:53 [Bug libc/9685] New: " vapier at gentoo dot org 2008-12-27 19:53 ` [Bug libc/9685] " vapier at gentoo dot org 2008-12-28 6:13 ` drepper at redhat dot com 2008-12-29 9:07 ` vapier at gentoo dot org 2009-02-07 5:20 ` drepper at redhat dot com 2009-02-07 6:28 ` vapier at gentoo dot org [this message] 2009-02-15 21:44 ` vapier at gentoo dot org [not found] <bug-9685-131@http.sourceware.org/bugzilla/> 2012-08-18 4:37 ` vapier at gentoo dot org 2014-07-02 7:46 ` 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=20090207062843.8775.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /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).