public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sandals at crustytoothpaste dot ath dot cx" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/2363] EOPNOTSUPP and ENOTSUP in errno.h must be different, according to SUSv3 Date: Mon, 20 Feb 2006 04:03:00 -0000 [thread overview] Message-ID: <20060220040306.25579.qmail@sourceware.org> (raw) In-Reply-To: <20060220024215.2363.sandals@crustytoothpaste.ath.cx> ------- Additional Comments From sandals at crustytoothpaste dot ath dot cx 2006-02-20 04:03 ------- If this is part of the ABI, then the ABI is broken. Just because things have always been one way does not mean that way is right, or even acceptable; an argument from tradition is a logical fallacy. Currently glibc claims to support SUSv3, by setting _POSIX_VERSION to 200112L. If it is not your intention to fix this, then please don't lie to the programmer and tell them you support a standard which you do not. -- What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|INVALID | http://sourceware.org/bugzilla/show_bug.cgi?id=2363 ------- 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:[~2006-02-20 4:03 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-20 2:42 [Bug libc/2363] New: " sandals at crustytoothpaste dot ath dot cx 2006-02-20 3:04 ` [Bug libc/2363] " drepper at redhat dot com 2006-02-20 4:03 ` sandals at crustytoothpaste dot ath dot cx [this message] 2006-02-20 4:31 ` drepper at redhat dot com 2006-12-06 22:18 ` samuel dot thibault at ens-lyon dot org [not found] <bug-2363-131@http.sourceware.org/bugzilla/> 2020-12-27 11:32 ` nicolas at debian dot org 2021-04-30 17:24 ` jwakely.gcc at gmail dot com 2021-05-11 13:31 ` nicolas at debian dot 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=20060220040306.25579.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).