public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "jnichols at alumni dot princeton dot edu" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug build/11278] New: Build errors in gdb 7.0.1 on Mac OSX Date: Sat, 13 Feb 2010 05:55:00 -0000 [thread overview] Message-ID: <20100213055503.11278.jnichols@alumni.princeton.edu> (raw) I'm getting numerous instances of this when I try to compile gdb 7.0.1 on Mac OSX 10.6.2 running Xcode tools 3.2.1 (gcc version 4.2.1 (Apple Inc. build 5646): warning: format not a string literal, argument types not checked since -Werror is set, the build fails. Here is an example of the warning/error from ppc-dis.c: fprintf (stream, _("\n\ The following PPC specific disassembler options are supported for use with\n\ the -M switch:\n")); The preprocessor spits this out: fprintf (stream, libintl_dgettext ("opcodes", "\nThe following PPC specific disassembler options are supported for use with\nthe -M switch:\n")); The build appears to fail when there are no arguments in the va_list when the _( ) macro is used. Not sure why it doesn't fail when there are arguments in the va_list. -- Summary: Build errors in gdb 7.0.1 on Mac OSX Product: gdb Version: 7.0 Status: UNCONFIRMED Severity: normal Priority: P2 Component: build AssignedTo: unassigned at sourceware dot org ReportedBy: jnichols at alumni dot princeton dot edu CC: gdb-prs at sourceware dot org http://sourceware.org/bugzilla/show_bug.cgi?id=11278 ------- 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:[~2010-02-13 5:55 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-02-13 5:55 jnichols at alumni dot princeton dot edu [this message] 2010-08-28 16:36 ` [Bug build/11278] " pedro at codesourcery 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=20100213055503.11278.jnichols@alumni.princeton.edu \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).