public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nszabolcs at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/18236] New: wchar.h does not define the va_list type Date: Fri, 10 Apr 2015 10:24:00 -0000 [thread overview] Message-ID: <bug-18236-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=18236 Bug ID: 18236 Summary: wchar.h does not define the va_list type Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: nszabolcs at gmail dot com CC: drepper.fsp at gmail dot com as an extension to ISO C, POSIX-2008 requires the va_list type to be defined in wchar.h http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/wchar.h.html the following code fails: #define _POSIX_C_SOURCE 200809 #include <wchar.h> void f() { va_list ap; // error: unknown type name 'va_list' } -- You are receiving this mail because: You are on the CC list for the bug.
reply other threads:[~2015-04-10 10:24 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-18236-131@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.org \ /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).