From: Tom Tromey <tromey@redhat.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: Tobias Hahn <tobias.hahn@ableton.com>, gdb@sourceware.org
Subject: Re: -Wformat and the like
Date: Fri, 09 Oct 2009 20:27:00 -0000 [thread overview]
Message-ID: <m3ocogb9ec.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4ACF80A8.9020206@codesourcery.com> (Stan Shebs's message of "Fri, 09 Oct 2009 11:27:52 -0700")
>>>>> "Stan" == Stan Shebs <stan@codesourcery.com> writes:
Tom> I don't know the answer, but I definitely don't see thousands of such
Tom> warnings on my Fedora 11 box.
Stan> I'm sure it's an OS X thing - the headers have all kinds of BSD-ish
Stan> and Mach-ish arcana that are different from other systems for, uh,
Stan> deeply-thought-out and carefully-documented reasons. :-) One could
Stan> get GDB to a clean build with OS X, but it would be a lot of macro
Stan> gymnastics.
Ah, I missed the --build in the original post.
We can easily filter these warnings by host.
This isn't ideal, but if system headers cause problems then I don't see
what else we can do.
Tom
prev parent reply other threads:[~2009-10-09 20:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 15:57 gdb-7.0 on osx Tobias Hahn
2009-10-08 16:02 ` Tristan Gingold
2009-10-08 16:56 ` Tobias Hahn
2009-10-09 7:55 ` Tristan Gingold
2009-10-09 9:39 ` Tobias Hahn
2009-10-09 13:05 ` Tristan Gingold
2009-10-09 8:04 ` Tristan Gingold
2009-10-09 12:56 ` Jack Howarth
2009-10-09 13:05 ` Tristan Gingold
2009-10-09 8:40 ` -Wformat and the like (was: gdb-7.0 on osx) Tobias Hahn
2009-10-09 8:53 ` Tobias Hahn
2009-10-09 17:51 ` -Wformat and the like Tom Tromey
2009-10-09 18:28 ` Stan Shebs
2009-10-09 18:44 ` Pedro Alves
2009-10-09 19:38 ` Tobias Hahn
2009-10-09 19:50 ` Daniel Jacobowitz
[not found] ` <02C5402A-7B26-4A21-91C2-549917DA523E@ableton.com>
2009-10-09 19:55 ` Pedro Alves
2009-10-12 9:51 ` Tristan Gingold
2009-10-12 14:32 ` Pedro Alves
2009-10-15 13:27 ` Tristan Gingold
2009-10-09 20:27 ` Tom Tromey [this message]
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=m3ocogb9ec.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=stan@codesourcery.com \
--cc=tobias.hahn@ableton.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