public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jsm28 at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/3440] locale.h macros like LC_ALL are not usable in #if
Date: Fri, 27 Apr 2012 10:50:00 -0000 [thread overview]
Message-ID: <bug-3440-131-k3SHYIb4ZT@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-3440-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=3440
Joseph Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |
AssignedTo|drepper.fsp at gmail dot |unassigned at sourceware
|com |dot org
--- Comment #5 from Joseph Myers <jsm28 at gcc dot gnu.org> 2012-04-27 10:50:20 UTC ---
Reopening. We discussed this general issue on #glibc last night. Paul, could
you update your patch for current glibc and send it to libc-alpha for review?
(Note: I have not checked if any standard C headers other than those mentioned
in this bug and bug 3439 are affected by similar issues. And I have not
checked if POSIX has the same requirement for integer constant expression
macros in POSIX headers, or what bugs there might be in POSIX headers if so.)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next parent reply other threads:[~2012-04-27 10:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-3440-131@http.sourceware.org/bugzilla/>
2012-04-27 10:50 ` jsm28 at gcc dot gnu.org [this message]
2012-05-10 12:42 ` jsm28 at gcc dot gnu.org
2006-10-31 20:08 [Bug libc/3440] New: " eggert at gnu dot org
2006-10-31 20:09 ` [Bug libc/3440] " eggert at gnu dot org
2006-11-10 16:24 ` drepper at redhat dot com
2006-11-10 19:06 ` eggert at gnu dot org
2007-02-17 8:59 ` drepper 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-3440-131-k3SHYIb4ZT@http.sourceware.org/bugzilla/ \
--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).