From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: asmwarrior <asmwarrior@gmail.com>, gdb@sourceware.org
Subject: Re: [mingw]gdb CVS HEAD build error
Date: Mon, 14 May 2012 04:58:00 -0000 [thread overview]
Message-ID: <20120514045808.GT29339@adacore.com> (raw)
In-Reply-To: <83k40fwk5k.fsf@gnu.org>
> > It suggest that under MinGW, we should use %I64d
> >
> > Any ideas?
>
> Use decimal2str?
We have plongest and pulongest which I think are a little more
convenient to use (it's based on decimal2str). Cast to LONGEST
instead of long long, and then pass it to plongest.
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, so it might not work in this case, but could be worth
a shot.
--
Joel
next prev parent reply other threads:[~2012-05-14 4:58 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 [this message]
2012-05-14 15:52 ` Eli Zaretskii
2012-05-14 16:16 ` Stan Shebs
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=20120514045808.GT29339@adacore.com \
--to=brobecker@adacore.com \
--cc=asmwarrior@gmail.com \
--cc=eliz@gnu.org \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).