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: Mon, 29 Dec 2008 09:07:00 -0000	[thread overview]
Message-ID: <20081229090631.18628.qmail@sourceware.org> (raw)
In-Reply-To: <20081227035150.9685.vapier@gentoo.org>


------- Additional Comments From vapier at gentoo dot org  2008-12-29 09:06 -------
sysdeps/unix/sysv/linux/kernel-features.h omits __sh__ from the list as it does
have pipe2 in linux-2.6.27, but that's a different issue

the point of the way glibc is laid out is for arches to control features like
this.  by binding sock_cloexec and pipe2 together without any sort of recourse,
you're basically saying that all other arches will be broken and there's nothing
they can do about it (regardless of whether they're in the "main" set of ports). 
if you want to add another define like __ASSUME_SOCK_CLOEXEC_AND_PIPE2 and key
the __have_pipe2->__have_sock_cloexec define off of that vs dedicated storage,
then that would work as the other arches would be able to disable it.

-- 


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.


  parent reply	other threads:[~2008-12-29  9:07 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 [this message]
2009-02-07  5:20 ` drepper at redhat dot com
2009-02-07  6:28 ` vapier at gentoo dot org
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=20081229090631.18628.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: 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).