public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "eggert at gnu dot org" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs-regex@sources.redhat.com Subject: [Bug regex/1233] New: regex.h POSIX and portability problems with REG_ENOSYS Date: Tue, 23 Aug 2005 20:17:00 -0000 [thread overview] Message-ID: <20050823201743.1233.eggert@gnu.org> (raw) regex.h defines REG_ENOSYS only if _XOPEN_SOURCE is defined. However, since 2001 POSIX has also required REG_ENOSYS, even if _XOPEN_SOURCE is not defined. Also, there is a problem with ifdeffing REG_ENOSYS out: that can cause the containing enum type to be unsigned rather than signed, which means that different object modules (compiled with and without _XOPEN_SOURCE, say) might not interoperate on some platforms. I'll attach a patch. -- Summary: regex.h POSIX and portability problems with REG_ENOSYS Product: glibc Version: 2.3.5 Status: NEW Severity: normal Priority: P2 Component: regex AssignedTo: gotom at debian dot or dot jp ReportedBy: eggert at gnu dot org CC: glibc-bugs-regex at sources dot redhat dot com,glibc- bugs at sources dot redhat dot com http://sources.redhat.com/bugzilla/show_bug.cgi?id=1233 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2005-08-23 20:17 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-23 20:17 eggert at gnu dot org [this message] 2005-08-23 20:18 ` [Bug regex/1233] " eggert at gnu dot org 2005-08-24 22:21 ` eggert at gnu dot org 2005-08-24 22:23 ` eggert at gnu dot org 2006-04-11 7:06 ` eggert at gnu 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=20050823201743.1233.eggert@gnu.org \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs-regex@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).