From: Stan Shebs <stan@codesourcery.com>
To: Masaki Muranaka <monaka@monami-software.com>
Cc: gdb-patches@sourceware.org, Daniel Jacobowitz <drow@false.org>
Subject: Re: State of old format warning patch for Mac OS X
Date: Wed, 23 Jul 2008 15:25:00 -0000 [thread overview]
Message-ID: <48874D23.7050508@codesourcery.com> (raw)
In-Reply-To: <E9C9ACBF-0F6C-4806-85E7-B5597E0AA286@monami-software.com>
Masaki Muranaka wrote:
> Hello,
>
> I guess GCC team have no interest in this issue as GCC is not built on
> OSX host.
> (Usually OSX hackers use GCC provided by Apple.)
>
> Then... what should I do to accept my patch.
I build GCC on OS X regularly, and don't remember seeing this warning,
so maybe nothing in GCC sources triggers it. In any case, as
src/intl/README says, this is a gettext patch ultimately and needs to go
to them.
But since I see that it has been years since gettext has been imported,
I'd say to just install this patch into src/ now - it's just a one-liner
and if by some chance it gets missed in a hypothetical future import,
it's easy to re-add. I'm guessing you don't have commit access? so I'll
take care of it.
Stan
>
> On 2008/07/15, at 8:00, Daniel Jacobowitz wrote:
>
>> On Mon, Jul 14, 2008 at 03:38:35PM -0700, Stan Shebs wrote:
>>> Whatever happened with Muranaka's patch in
>>> http://sourceware.org/ml/gdb-patches/2007-02/msg00160.html to fix the
>>> "format not a string literal" warnings on Mac OS X? I've been getting
>>> those complaints from vec.h expansions, this patch shuts them off very
>>> nicely.
>>
>> Nothing past the response in the list archives, AFAIK.
>>
>> --
>> Daniel Jacobowitz
>> CodeSourcery
>>
>
> Masaki Muranaka
> Monami Software
>
>
>
>
>
next prev parent reply other threads:[~2008-07-23 15:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 22:39 Stan Shebs
2008-07-14 23:00 ` Daniel Jacobowitz
2008-07-23 12:35 ` Masaki Muranaka
2008-07-23 15:25 ` Stan Shebs [this message]
2008-07-23 15:40 ` Daniel Jacobowitz
2008-12-14 5:03 ` Masaki Muranaka
2008-12-17 15:48 ` Ian Lance Taylor
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=48874D23.7050508@codesourcery.com \
--to=stan@codesourcery.com \
--cc=drow@false.org \
--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