Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Masaki Muranaka <monaka@monami-software.com>
Cc: Andreas Schwab <schwab@suse.de>, gdb-patches@sourceware.org
Subject: Re: [patch] Failed to build mips64-elf with NLS on OSX
Date: Thu, 15 Jun 2006 13:51:00 -0000	[thread overview]
Message-ID: <20060615135139.GA17504@nevyn.them.org> (raw)
In-Reply-To: <FC089432-0F37-4019-B500-068B7AA688CD@monami-software.com>

On Thu, Jun 15, 2006 at 08:34:06PM +0900, Masaki Muranaka wrote:
> 
> Still I was confused, but I see somehow.
> 
> On 2006/06/15, at 19:04, Masaki Muranaka wrote:
> >internal_error ("../../src/gdb/mips-tdep.c", 273, libintl_gettext  
> >("bad switch"));
> 
> As Schwab says, dgettext/gettext was regarded as constant by gcc.
> The information was put on gcc/builtin.def.
> So there is no troubles on some targets which expands _() to dgettext().
> I checked the code generated on Linux. _() was expanded to
> dgettext().
> 
> But the another target which expands _() to libintl_gettext(),
> the build will be failed. Because there is no information
> about libintl_gettext() in builtin.def.
> The code which is generated on MacOSX was so.
> 
> If my understanding is reasonable, -Wformat-nonliteral
> should be off in case GDB is built with intl/, right?
> (Fixing GCC or intl is also not impossible, but I don't want to)

But it's right :-)

char *libintl_gettext (const char *) __attribute__((format_arg(1)));

That's enough to fix it.  The example in the manual is even a dgettext
wrapper.  It looks like it's been there since ~ 2001.  There's already
a GNUC version check in libgnuintl.h; adding another one with the
appropriate version ought to fix this.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-06-15 13:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-15  8:12 Masaki Muranaka
2006-06-15  8:22 ` Andreas Schwab
2006-06-15  9:12   ` Masaki Muranaka
2006-06-15  9:24     ` Andreas Schwab
2006-06-15 10:04       ` Masaki Muranaka
2006-06-15 11:34         ` Masaki Muranaka
2006-06-15 13:51           ` Daniel Jacobowitz [this message]
2006-06-16  0:42             ` Masaki Muranaka

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=20060615135139.GA17504@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=monaka@monami-software.com \
    --cc=schwab@suse.de \
    /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