Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: Masaki Muranaka <monaka@monami-software.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Failed to build mips64-elf with NLS on OSX
Date: Thu, 15 Jun 2006 09:24:00 -0000	[thread overview]
Message-ID: <je3be6bwkf.fsf@sykes.suse.de> (raw)
In-Reply-To: <6E68F226-6A7E-4DB7-8734-A448045A6129@monami-software.com> 	(Masaki Muranaka's message of "Thu, 15 Jun 2006 18:12:15 +0900")

Masaki Muranaka <monaka@monami-software.com> writes:

> On 2006/06/15, at 17:22, Andreas Schwab wrote:
>> GCC should recognize gettext specially in the context of format string
>> tests.
>
> Regardless GCC should work so, the build was failed.

GCC _does_ work so.

> This is a sample script that reproduce the error.
> I tested on gcc-4.0.1/OSX and gcc-3.2.2/Linux.
> Results are same.
>
> -8<----8<----8<----8<----8<----8<---
> cat <<__EOF > test.c
> #include <stdio.h>
>
> # define _(String) gettext (String)
>
> int
> main(int argc, char **argv)
> {
>         printf(_("aaa"));
> }
> __EOF
> gcc -Werror -Wformat -Wformat-nonliteral -c test.c
> -8<----8<----8<----8<----8<----8<---

This is not a valid testcase since gettext is not declared.

I cannot reproduce the problem with any gcc version, once the missing
declaration is added.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."


  reply	other threads:[~2006-06-15  9:24 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 [this message]
2006-06-15 10:04       ` Masaki Muranaka
2006-06-15 11:34         ` Masaki Muranaka
2006-06-15 13:51           ` Daniel Jacobowitz
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=je3be6bwkf.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=monaka@monami-software.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