From: Stan Shebs <stanshebs@earthlink.net>
To: gdb@sourceware.org
Subject: Re: [mingw]gdb CVS HEAD build error
Date: Mon, 14 May 2012 16:16:00 -0000 [thread overview]
Message-ID: <4FB12FB4.1070407@earthlink.net> (raw)
In-Reply-To: <83ipfywyga.fsf@gnu.org>
On 5/14/12 8:53 AM, Eli Zaretskii wrote:
>> Date: Sun, 13 May 2012 21:58:08 -0700
>> From: Joel Brobecker<brobecker@adacore.com>
>> Cc: asmwarrior<asmwarrior@gmail.com>, gdb@sourceware.org
>>
>> Another possible option is to switch to gnulib's printf. I don't know
>> if gnulib's configury would detect faulty or incomplete versions of
>> printf like here
> This is not an incomplete implementation, it's just that we are using
> an unportable format specifier. We should be using what inttypes.h
> says (or use LONGEST and plongest).
>
Yeah, I'll take care of this, I habitually forget about mingw not liking
those directives.
Stan
prev parent reply other threads:[~2012-05-14 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 1:24 asmwarrior
2012-05-14 2:49 ` Eli Zaretskii
2012-05-14 4:58 ` Joel Brobecker
2012-05-14 15:52 ` Eli Zaretskii
2012-05-14 16:16 ` Stan Shebs [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=4FB12FB4.1070407@earthlink.net \
--to=stanshebs@earthlink.net \
--cc=gdb@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: 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