public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msm at freescale dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug stdio/13775] New: dprintf and vdprintf are undefined if -D_GNU_SOURCE Date: Mon, 27 Feb 2012 21:18:00 -0000 [thread overview] Message-ID: <bug-13775-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13775 Bug #: 13775 Summary: dprintf and vdprintf are undefined if -D_GNU_SOURCE Product: glibc Version: 2.13 Status: NEW Severity: normal Priority: P2 Component: stdio AssignedTo: unassigned@sourceware.org ReportedBy: msm@freescale.com Classification: Unclassified See the following errors: # gcc -o test -D_GNU_SOURCE test.c In file included from /usr/include/stdio.h:933:0, from test.c:1: /usr/include/bits/stdio-ldbl.h:67:1: error: 'vdprintf' undeclared here (not in a function) /usr/include/bits/stdio-ldbl.h:68:1: error: 'dprintf' undeclared here (not in a function) test.c: In function 'main': test.c:9:16: error: called object 'dprintf' is not a function Seems to be related to in appropriate ifdef. Full test case below: https://gist.github.com/1927104 -- 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 reply other threads:[~2012-02-27 21:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-02-27 21:18 msm at freescale dot com [this message] 2012-02-27 21:23 ` [Bug stdio/13775] " roland at gnu dot org 2012-02-27 22:04 ` roland at gnu dot org 2012-02-28 17:01 ` msm at freescale dot com 2012-02-28 17:36 ` roland at gnu dot org 2014-06-26 14:18 ` 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=bug-13775-131@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: 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).